Loading ToolBench
Single tool with minimal schema and generic description. Description is 234 chars (within baseline 194 avg), but lacks actionable context for LLM selection. No parameter descriptions exist (N/A due to empty schema). No output schema documented. No error handling guidance. Tool does one thing (return docs) but lacks production-grade polish.
This tool returns instructions on how to build MCP servers. You should use this tool if the user asks you to make an MCP server, but did not provide general information on MCP servers. The instructions include an example server and a quick overview of MCP terms like tools, resources, and prompts.
Empty input schema ({}). Tool accepts no parameters, which is valid, but schema must be explicitly documented as empty object with type 'object' and properties: {}.
No output schema documented. LLM cannot infer return type (string vs object vs array). Baseline: 100% of A+ tools have documented return types.
Description lacks WHEN to use guidance. Current: 'This tool returns instructions...' Better: 'Call this when user asks how to build MCP servers but provides no context. Returns step-by-step guide with example server code and MCP terminology (tools, resources, prompts).'
No error handling guidance. What if docs.md is missing? Tool will crash. Should catch FileNotFoundError and return actionable error: 'Documentation file not found. This is a server configuration error, contact administrator.'
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 32 | 2026-07-28+ | v2 |
Tool name 'how_to_make_mcp' does not start with action verb. Baseline: 90% of A+ tools start with verb (get, create, search, list, etc.). Better: 'get_mcp_documentation' or 'describe_mcp_server_building'.