MCP server for analytics operations with tools, resources, and prompts
Single tool 'calculate_metric' has critical gaps. Description is minimal (27 chars, below 20-char floor). Input parameters lack descriptions entirely (null values visible in schema). No output schema documented. Tool name 'calculate_metric' is vague, does not follow verb_noun pattern and does not clarify what metric or when to use it. No error handling, validation, or recovery guidance. Rubric baseline: 94% of A+ tools have param descriptions; 100% have documented return types. This server meets neither.
Calculate an important metric
Tool description too short (27 chars). Rubric floor is 20 chars minimum; A+ baseline is 50-200 chars. Current description 'Calculate an important metric' does not explain WHAT metric, WHEN to use it, or WHAT it returns.
All input parameters lack descriptions (null values in schema). Rubric requires non-empty description for every parameter. LLMs cannot infer that 'value1' and 'value2' are multiplied and divided by 100 without explicit guidance.
No output schema documented. Rubric baseline: 100% of A+ tools have documented return types. Callers do not know the output is a float, its range, or units.
Tool name 'calculate_metric' is vague and does not follow verb_noun pattern. Does not start with action verb (get_, create_, search_, etc.). 'Metric' is ambiguous, could be any calculation. Rubric: 90% of A+ tools start with action verb.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 27 | 2026-07-28+ | v2 |
No error handling or validation. Tool accepts unbounded floats with no range constraints, validation, or recovery guidance. Rubric requires: 'Error responses must tell the LLM what to do next' and 'Include the invalid value and constraint violated.'