MCP server for interacting with Elevar's API for analytics and data management
Server has 5 tools with explicit Zod schemas and descriptions. Naming follows verb_noun convention (create_, update_, delete_, query_, get_). However, descriptions are minimal (10-50 chars), parameter descriptions lack detail on constraints/formats, and output schemas are not documented. Error handling returns isError flag but lacks recovery guidance. No tool annotations (readOnlyHint/destructiveHint). Resource definitions present but not integrated with tool composition.
Create a new data source in Elevar
Delete a data source from Elevar
Get available metrics and dimensions for a data source
Query data from an Elevar data source
Update an existing data source in Elevar
Tool descriptions are too brief (10-50 chars). Rubric baseline is 194 chars. LLMs cannot determine when/why to select tools without context on prerequisites, return values, and use cases.
No output schema documentation. Tools return JSON text blobs without field definitions. LLMs cannot plan downstream calls or extract structured data reliably.
Missing tool annotations. delete_data_source and update_data_source lack destructiveHint/idempotentHint. Agents cannot distinguish safe-to-retry operations from irreversible ones.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 45 | 2026-07-28+ | v2 |
Error messages lack recovery guidance. Errors return raw error.message without suggesting next steps (e.g., 'Try search_data_sources() first'). Agents cannot self-correct.
Parameter descriptions lack constraint details. 'metrics' and 'dimensions' are arrays of strings with no format/length guidance. 'filters' object schema is present but not explained in parameter description.