Loading ToolBench
Free MCP server with pre-built AI agent blueprints for common business processes. No signup required.
Two tools with basic schemas and descriptions, but significant gaps in parameter documentation and output schema clarity. list_blueprints has empty input schema (correct for no-param tool) but lacks output documentation. get_blueprint has one parameter with description, but no output schema documented. Both descriptions are adequate (100-150 chars) but lack actionable guidance on when/why to use them. No error recovery hints. No tool annotations. Naming is clear (verb_noun pattern). Overall: functional but below production baseline.
Download a free AI agent blueprint by ID. Returns a JSON manifest with all files (SKILL.md, reference docs, implementation guide) ready to write to disk. Same format as the paid Agent Blueprint export.
List available free AI agent blueprints. Returns catalog of pre-built blueprints for common business processes. No signup or API key required.
Output schemas not documented. LLMs cannot infer what fields to expect from list_blueprints (catalog structure?) or get_blueprint (manifest format?). Agents cannot plan downstream operations without knowing response shape.
No error recovery guidance. get_blueprint returns isError=true with a message when blueprint not found, but description does not mention this failure mode or suggest recovery (e.g., 'Call list_blueprints first to see available IDs'). LLM has no guidance on what to do next.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Both tools are read-only and idempotent, but this is not declared in the schema. Agents cannot infer safety properties without explicit hints.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 54 | 2026-07-28+ | v2 |
list_blueprints description lacks context on when to call it. Should state: 'Call this first to discover available blueprint IDs before calling get_blueprint.' Dependency hints prevent wasted calls.
get_blueprint parameter 'blueprintId' description is minimal ('Blueprint ID from list_blueprints'). Should specify format constraints, e.g., 'Alphanumeric ID (2-50 chars, lowercase with hyphens). Obtain from list_blueprints.'