MCP server with OAuth 2.0 authorization provider running on Cloudflare Workers, demonstrating remote MCP authentication and authorization flows
Single tool 'add' has a clear verb-noun name and basic schema with typed parameters. However, the description is minimal (22 chars) and lacks context about when/why to use it. Parameters 'a' and 'b' have type definitions and brief descriptions, meeting baseline requirements. No output schema is documented. The tool is trivial (arithmetic) and does not reflect production patterns like error handling, idempotency hints, or composition guidance. Baseline: 194 chars avg description, 72 chars avg param annotation. This server falls well below production quality.
Adds two numbers together
Tool description is 22 characters, below the 10 - 1024 character guideline and lacks context. Does not explain WHEN to use this tool, what it returns, or any prerequisites.
Output schema is not documented. LLMs cannot plan downstream calls or extract results without knowing the response structure.
No error handling guidance. Tool does not document what happens on invalid input (e.g., non-numeric values, overflow) or how the LLM should recover.
No tool annotations (readOnlyHint, idempotentHint, destructiveHint). The 'add' tool is read-only and idempotent, but these hints are not declared in the schema.
Single trivial tool does not demonstrate composition patterns. No batch operations, pagination, or chaining support.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 47 | 2026-07-28+ | v2 |