OpenAI-compatible gateway that augments any LLM with a reusable fabric of MCP servers.
All three tools have minimal descriptions (10-34 chars, well below the 50-200 char LLM-optimized baseline) and critically, ALL parameter descriptions are null/missing. Input schemas exist but lack parameter-level documentation. Tool names are simple verbs (add, echo, uppercase) but descriptions are too terse to guide LLM selection. No output schemas documented. No error handling guidance. This is a toy example server, not production-grade.
Add two numbers and return the sum.
Echo back the provided text.
Return the text uppercased.
All parameter descriptions are null. Parameters 'a', 'b', 'text' have no descriptions explaining their purpose, format, or constraints.
Tool descriptions are too short (10-34 chars vs 50-200 char baseline). 'Add two numbers and return the sum.' lacks context on when to use this vs other tools, prerequisites, or return format.
No output schemas documented. LLMs cannot infer what fields or types are returned, forcing them to guess downstream tool compatibility.
No error handling guidance. Tools do not document what errors are possible, whether they are retryable, or what the LLM should do if a call fails.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 41 | 2026-07-28+ | v2 |
Parameter types are inferred from Python type hints (float, string) but not explicitly documented in descriptions. LLMs cannot read JSON Schema type fields, they rely on description text.