MCP proxy server that filters tools from upstream MCP servers via regex-based deny list
Scoring was not performed
Missing output schema documentation. Neither tool documents its return type, structure, or field meanings. Callers (LLMs) cannot predict what fields are available, forcing them to guess or fail.
Insufficient parameter descriptions. The 'arguments' parameter in call_tool has generic description ('Arguments to pass to the tool') with no format, constraints, or validation rules. LLMs cannot determine valid input structure.
No recovery guidance in error responses. When a tool is blocked (code -32601), the message 'Tool not found: {name}' provides no actionable next step. Should suggest: 'Tool is blocked by deny pattern. Call list_tools() to see allowed tools.'
Tool descriptions lack context on filtering behavior and prerequisites. Descriptions do not explain what deny patterns are, how to discover blocked tools, or when to use list_tools before call_tool.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 29 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 27 | - | v1 |
Descriptions are below recommended length. list_tools (48 chars) and call_tool (58 chars) are below the 194-char baseline for production tools. Expand to explain WHAT, WHEN, and WHY.