This is a minimal evaluation framework repository, not a production MCP server. The single example tool 'add' in examples/simple-tools-server/src/server.ts is deliberately simplistic and not representative of real-world tool design. The tool has a valid Zod schema and basic description, but lacks production-grade documentation, error handling guidance, and parameter descriptions required by the rubric. The repository itself is a testing/evaluation harness (@buildwithlayer/mcp-evals) rather than a tool provider.
Tool 'add' has no description in server definition. Line: server.ts tool registration lacks 'description' field.
Parameters 'a' and 'b' lack human-readable descriptions. Only Zod type constraints present; LLMs cannot understand what these parameters control beyond their type.
No output schema documentation. Response structure is inferred from the handler code ({content: [{text, type}]}) rather than formally specified for LLM consumption.
No error handling guidance. Tool lacks try-catch or validation; LLM has no recovery instruction if invalid input is passed.
Tool name 'add' is generic and lacks verb_noun clarity. Does it add to a list, add numbers, or add a record to a database? For a math operation, consider 'calculate_sum' or 'sum_numbers'.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 43 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 0 | - | v1 |