Loading ToolBench
AgentLock authorization middleware for MCP (Model Context Protocol) servers.
Two tools with minimal descriptions (10-15 chars each) and incomplete parameter documentation. web_fetch lacks description of return format and error cases. send_email missing 'subject' parameter and lacks guidance on when to use it vs alternatives. No output schemas documented. Parameter descriptions absent entirely. No error handling guidance. Schemas present but sparse, only type and required fields, no constraints or format hints. This is a basic example server, not production-grade.
Send an email.
Fetch a web page.
Tool descriptions critically short (10-15 chars). 'Fetch a web page' and 'Send an email' lack context for LLM selection. No guidance on when to use each tool, what it returns, or error recovery.
No parameter descriptions. 'url', 'to', 'body' lack explanations of format, constraints, or expected values. LLMs cannot infer whether 'url' accepts relative paths, whether 'to' is email or username, or if 'body' supports HTML.
send_email missing 'subject' parameter. Real email requires a subject line. Current schema only accepts 'to' and 'body', forcing agents to invent subjects or fail.
No output schemas documented. web_fetch returns TextContent but LLMs don't know the structure. send_email returns confirmation but format is undocumented. Agents cannot plan downstream calls without knowing response shape.
Inferred effective spec: 2026-07-28+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 42 | 2026-07-28+ | v2 |
No error handling guidance. If web_fetch hits a 404 or timeout, or send_email fails due to invalid recipient, the tool returns nothing actionable. LLM has no recovery path.