Three tools with basic schemas and descriptions, but significant gaps in parameter documentation and output schema clarity. All tools are READ_ONLY and follow verb_noun naming (get_*), which is correct. However, parameter descriptions lack detail on constraints, formats, and valid ranges. Output schemas are not documented, LLMs cannot plan downstream calls or extract structured data. Error handling exists at the server level but tools lack recovery guidance. No tool annotations (readOnlyHint, etc.) despite all being read-only.
Get trending error patterns and their impact.
Get impact analysis of errors on users/sessions.
Get project-wide error statistics.
Output schemas not documented. LLMs cannot infer what fields are returned, breaking downstream tool chaining and forcing wasteful discovery calls.
Parameter descriptions lack format/constraint details. 'time_range' accepts '24h', '7d', 'all' but description does not enumerate valid values or explain format. LLMs will guess and pass invalid values.
No tool annotations despite all tools being read-only. readOnlyHint should be set to true on all three tools to signal safety to agents.
'min_occurrences' parameter in get_error_trends lacks numeric bounds. Description should specify min/max range (e.g., 1 - 10000) to prevent LLM from passing absurd values.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 51 | <=2025-11-25 | v2 |
Tool descriptions are generic and lack WHEN/WHY guidance. 'Get project-wide error statistics' does not explain when to call this vs get_error_trends or get_impact_analysis. LLMs cannot disambiguate.