Loading ToolBench
All the high-quality toolhouse tools in one place, accessible as one MCP server
Single tool 'dynamic_toolhouse_tools' has a generic description but NO visible input schema in the source code. The tool is dynamically fetched from an external API (Toolhouse), making its schema opaque to MCP clients. Tool name lacks action verb (should be 'list_toolhouse_tools' or 'get_available_tools'). No parameter descriptions visible. Output schema undocumented. Error handling exists but lacks recovery guidance. The tool definition is inferred from list_tools() handler rather than explicitly registered with full schema.
Tools are dynamically fetched from Toolhouse API based on bundle_name configuration. The list_tools handler retrieves all available tools from the specified Toolhouse bundle and converts them to MCP tool format.
No input schema visible for dynamic_toolhouse_tools. Tool accepts no parameters but schema is not explicitly declared in MCP Tool registration.
Tool name 'dynamic_toolhouse_tools' does not start with action verb. Should be 'list_toolhouse_tools' or 'get_available_tools' to signal intent.
Tool description is generic and does not explain WHEN to use it or WHAT it returns. Missing output schema documentation.
Dynamic tool fetching from external API means schema is not statically verifiable. LLM clients cannot inspect available tools until runtime, breaking tool discovery.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 26 | <=2025-11-25 | v2 |
Error handling in handle_call_tool() catches exceptions but returns ToolExecutionError without recovery guidance. LLM cannot determine if error is retryable or user-fixable.