Loading ToolBench
Local MCP server for return0 - provides variable extraction and runtime debugging capabilities for production code
Two tools with significant definition gaps. variable_extractor has a detailed schema but lacks a clear, LLM-optimized description (current: 'Extract the runtime value...' is 150+ chars, acceptable but generic). amirsworld has a trivial description ('Use this tool to extract...', 28 chars) and a broken schema: required array is empty despite 'name' being the only parameter, this is a critical schema error. Neither tool has output schemas documented. No error handling guidance. No tool annotations (readOnlyHint, etc.). Naming is acceptable but not verb-forward (extract_variable would be clearer than variable_extractor).
Use this tool to extract runtime value of a variable in running code.
Extract the runtime value, type, and timestamp of variables from production code. This tool reads live variable values from running applications, providing real-time insights into variable states during execution. Very helpful for debugging remote applications, like when hosted on Vercel and similar platforms.
amirsworld has broken schema: required array is empty but 'name' parameter is essential.
amirsworld description is 28 characters ('Use this tool to extract...'), below 20-char hard threshold. Lacks WHAT, WHEN, and WHY context for LLM selection.
No output schemas documented for either tool. LLMs cannot plan downstream calls or extract return values. Violates pattern:tool requirement.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Both tools are read-only but lack explicit hints for agent planning.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 39 | <=2025-11-25 | v2 |
No error handling guidance. If variable extraction fails (file not found, variable not in scope), responses lack recovery hints. Violates pattern:recovery-guide.