MCP server with OAuth 2.0 authorization provider running on Cloudflare Workers, demonstrating remote authentication 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. No error handling guidance. The tool is trivial (arithmetic) and does not demonstrate production-grade patterns like pagination, error recovery, or composition with other tools. This is a demo server, not a production-ready implementation.
Adds two numbers together
Tool description is too brief (22 chars). Lacks context on when to use, prerequisites, or return value structure. LLMs need 50-200 char descriptions to make informed selection decisions.
Output schema is not documented. The tool returns text content, but the response structure is not declared. LLMs cannot plan downstream calls or extract data without knowing the output shape.
No error handling or recovery guidance. If inputs are invalid (non-numeric), the tool will fail silently. No guidance for the LLM on what to do next.
Tool is trivial and does not demonstrate composition patterns. A single arithmetic operation does not show how this server would scale to multi-step workflows or chained tool calls.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 48 | 2026-07-28+ | v2 |