An MCP server deployed on Cloudflare Workers with OAuth 2.0 authentication support, demonstrating remote MCP server capabilities with a simple arithmetic tool
Single tool 'add' has critical definition gaps. Input schema present with Zod types (a, b as numbers) but parameter descriptions are null, violates the requirement that every parameter needs a description. Tool description is missing entirely (no docstring visible in registration). Output schema not documented. No error handling guidance. Naming is acceptable (verb_noun pattern) but insufficient to overcome missing descriptions and documentation.
Tool 'add' has no description. LLMs cannot determine when or why to select this tool without a docstring explaining its purpose, when to use it, and what it returns.
All input parameters (a, b) have null descriptions. Parameter descriptions are mandatory, LLMs cannot infer that 'a' and 'b' are operands for addition without explicit text.
Output schema is not documented. The tool returns text content but LLMs have no formal specification of the response structure, forcing them to guess at field names and types.
No error handling guidance. If the tool fails (e.g., invalid input types), there is no recovery path or actionable error message for the LLM.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 35 | 2026-07-28+ | v2 |
Tool serves only arithmetic addition, extremely limited scope. No context for when an agent would call this vs. other tools or how it fits into a larger workflow.