Loading ToolBench
A FastMCP server that provides a greeting tool and health check endpoint
Single tool 'greet' has a basic description but lacks depth. Input schema is present with proper type (string) and parameter description, meeting minimum requirements. However, the tool description is only 24 characters ('greet the user by name'), which is at the lower end of the 10-1024 character baseline. No output schema is documented, LLMs cannot predict the response structure. No error handling guidance, no parameter constraints, and no indication of idempotency or side effects. The tool is trivial (READ_ONLY greeting), but even simple tools should follow pattern standards for consistency.
greet the user by name
Missing output schema documentation. Tool returns a string but LLMs cannot infer the response structure or plan downstream operations.
Tool description is minimal (24 chars). Should explain WHAT it does, WHEN to use it, and WHAT it returns. Current description lacks context for LLM selection.
No error handling guidance. If name is empty or invalid, what should the LLM do? No recovery path documented.
Parameter 'name' lacks constraints. No minimum/maximum length, no format specification, no guidance on handling special characters or empty strings.
No tool annotations present. Should declare idempotentHint=true since greeting is a read-only, side-effect-free operation.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 47 | 2026-07-28+ | v2 |