Drop-in Google OAuth 2.0 authentication for MCP servers
Two tools with minimal definitions. Both have descriptions (10-20 chars, below baseline 194 chars) and basic parameter schemas, but lack depth. 'hello' and 'add' are generic utility tools with trivial functionality. Descriptions are too short to guide LLM selection. Parameters have types but lack detailed constraints or usage guidance. No output schema documentation. No error handling guidance. No composition or chaining support. This is a demo/example server, not production-grade.
Add two numbers together.
Say hello. Use this to verify the MCP connection is working.
Descriptions are too short (10-20 chars vs baseline 194 chars). 'Say hello' and 'Add two numbers together' lack context for LLM selection, when to use, or what to expect.
No output schema documented. LLMs cannot plan downstream calls or extract structured data from responses.
Tool names are generic verbs without clear domain context. 'hello' and 'add' do not convey business intent or distinguish from similar tools in a larger toolkit.
Parameter descriptions are minimal. 'Name to greet' and 'First number' lack format constraints, ranges, or usage examples.
Inferred effective spec: 2026-07-28+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 49 | 2026-07-28+ | v2 |
No error handling guidance. Tools do not document failure modes, recovery steps, or what LLMs should do if a call fails.