Loading ToolBench
Custom MCP server with plugin system, proxy support, and built-in tools for math, crypto, datetime, filesystem, system, and text utilities
AIX MCP Server provides 16 tools with explicit schemas and descriptions. Most tools have clear verb-noun naming (echo, hash-text, read-file, run-command) and documented input parameters with types and enums. However, descriptions are often terse (10-50 chars), parameter descriptions lack context about constraints and formats, and output schemas are not documented. The proxy tools (proxy-call, proxy-list-targets, proxy-{target}-tools) are inferred rather than explicitly registered, capping their scores. Error handling is minimal, no recovery guidance or actionable error messages visible. Security concerns: run-command is DESTRUCTIVE with no confirmation pattern, and list-files/read-file lack path traversal validation hints.
Encode text to Base64 or decode Base64 into UTF-8 text
Evaluate a mathematical expression and return the result
Get the current date and time in ISO, locale, or Unix timestamp format
Echoes back your message with an optional prefix
Format an ISO date string or Unix timestamp
Create a digest for text using sha256, sha512, or md5
Parse and pretty-print JSON text
run-command is DESTRUCTIVE but lacks confirmation pattern or dry-run support. No error recovery guidance. Description does not warn of irreversible consequences.
Descriptions are terse (10-60 chars) and lack context. 'Get the current date and time' does not explain when to use it vs format-time, or what format is returned. Descriptions should be 50-200 chars with WHEN/WHY guidance.
Output schemas are not documented. Tools return structured responses but LLMs cannot see what fields to expect. Responses should be documented in tool descriptions or via explicit schema declarations.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 57 | <=2025-11-25 | v2 |
List files and directories at the given path
Forward a method call to a remote MCP server. Available targets: [dynamic based on mcp-proxy.json]
List all available proxy targets and their status
List tools available on remote server: {target}
Generate a cryptographically random string
Generate one or more random UUID v4 values
Read the contents of a text file
Execute a shell command and return the output
Count characters, words, lines, and bytes in text
Proxy tools (proxy-call, proxy-list-targets, proxy-{target}-tools) are inferred from code rather than explicitly registered with visible schemas. Tool definitions are not directly visible in source.
list-files and read-file lack path traversal validation hints. Descriptions do not warn about security constraints or mention that paths are validated server-side.