Loading ToolBench
MCP server for the DevEx cloud IDE platform, providing tools for workspace management, file operations, and terminal interaction with Kubernetes-based containers
Single tool 'FetchContent' with minimal schema definition and inadequate descriptions. Tool name lacks action verb prefix. Input parameter has basic type but no validation constraints. No output schema documented. No error handling guidance. Does not follow verb_noun naming pattern (should be 'get_file_content' or similar). Descriptions are bare-minimum, providing almost no context for LLM selection or usage.
Fetch file content from workspace filesystem
Tool name 'FetchContent' does not start with action verb. Naming convention should be 'get_file_content', 'read_file', or 'fetch_file_content' to signal intent to LLMs before they read the description.
Tool description 'Fetch file content from workspace filesystem' is only 43 characters. Too brief to guide LLM selection. Should explain: What does it do? When to use it? What does it return? What constraints apply (max file size, allowed paths)?
Input parameter 'Path' lacks description entirely. Parameter descriptions are required so LLMs understand what values to pass. Should clarify: Is it relative or absolute? Any restrictions (e.g., no parent directory traversal)? Max length?
No output schema documented. LLMs need to know what fields to expect in the response (e.g., file_content, file_size, encoding, error messages). Without this, agents cannot plan downstream operations or extract relevant data.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 32 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 36 | - | v1 |
No error handling guidance. Tool should document what errors are possible (file not found, permission denied, path traversal attempt) and what the LLM should do next (which tool to call, how to recover).
No input validation constraints documented. Tool accepts a 'Path' string with no stated restrictions, inviting potential security issues (path traversal). Description should explicitly state: 'Paths must be relative to workspace root. Parent directory traversal (..) is rejected.'
No pagination or result size limits documented. If files can be large, tool should cap response size, support partial reads, or document max file size to prevent context window exhaustion.