MCP server with OAuth2 authentication support using Affinidi as identity provider
This server has three tools with moderate structural support but significant quality gaps. All three tools have basic Zod schemas (a+, b, message, weightKg, heightM) and short descriptions, but critically lack parameter-level documentation. Parameter descriptions are all null in the schema, which is a hard blocker for LLM understanding. Tool names are reasonably action-oriented (add, echo, calculate-bmi) but descriptions are too terse (10-26 chars each, below the 34-char p10 baseline). No output schemas are documented. No error handling guidance is provided. The server includes OAuth2 infrastructure and prompts/resources, which is good for protocol breadth, but the core tool quality is below production grade.
Add two numbers
Calculate BMI from weight and height
echo a message
All parameter descriptions are null. Input schema shows `{"a":{"type":"number","description":null},...}`. Parameters lack explanations of their role, valid ranges, or constraints.
Tool descriptions are too short (10-26 characters). 'Add two numbers', 'echo a message', 'Calculate BMI from weight and height' lack context on WHEN to use, WHAT the output means, or any dependencies. Baseline: 34 chars p10, 194 chars average.
No output schemas documented. Tools return `{ content: [{ type: "text", text: String(...) }] }` but LLMs cannot plan downstream steps without knowing the response structure. LLMs need to know what fields to expect so they can plan downstream tool calls.'
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | D | 51 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 48 | - | v1 |
Parameter names lack clarity and differentiation. 'a' and 'b' in add() are cryptic, should be 'first_number' and 'second_number'. 'heightM' and 'weightKg' mix units in names (suffix notation), should be 'height_meters' and 'weight_kilograms'. Ambiguous names cause LLMs to guess wrong.'
No error handling guidance. Tools have no validation logic visible; if 'a' or 'b' in add() is NaN or Infinity, or if heightM is zero in calculate-bmi (division by zero), no error recovery hint is provided.
No numeric constraints documented. Parameters 'a', 'b', 'weightKg', 'heightM' accept arbitrary Zod numbers. No min/max, no range guidance. Unbounded numbers let LLMs pass absurd values.'
Tool composition is weak. 'add' and 'calculate-bmi' are narrow utilities with no chaining to other tools shown. The server defines 2 resources (echo, greeting) alongside 3 tools, but no clear use case flows.