Local, read-only observability workbench for reviewable telemetry reduction drafts
Four read-only tools with basic schemas and descriptions. All tools have input schemas with required parameters properly typed. Descriptions are present but minimal (10-80 chars, below the 194-char baseline). No parameter descriptions visible in schemas, parameters lack inline documentation explaining their purpose. Output schemas are not documented. Error handling is absent, no guidance on recovery or retryable conditions. Tool names follow verb_noun pattern (search_, get_, analyze_, search_) which is good, but descriptions lack context on when to use each tool vs. alternatives. The server implements tool annotations (readOnlyHint) correctly, but this alone cannot compensate for missing parameter docs and output schemas.
Return a deterministic normalized aggregate of sample logs. Raw records are not returned.
List environments for a sample service. Read-only.
Return a small set of already-redacted sample records when examples are required. Read-only.
List services with bundled sample log telemetry. Read-only.
Parameter descriptions missing. Schemas define required parameters (service, timeWindow, environment, limit) but provide no descriptions explaining what each controls or how to format them. LLMs cannot infer parameter semantics from names alone.
Output schemas not documented. Tools return data but no schema is visible describing the structure, field types, or what fields to expect. Agents cannot plan downstream calls or extract data reliably.
Tool descriptions are too brief (10-80 chars vs. 194-char baseline). Descriptions lack context on WHEN to use each tool, what distinguishes analyze_logs from search_logs, or what data structure is returned. LLMs cannot reliably select the right tool.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 55 | 2025-06-18+ | v2 |
No error handling or recovery guidance. Tools provide no error messages, retryability hints, or guidance on what to do if a service is not found or timeWindow is invalid. Agents cannot self-correct.
timeWindow parameter lacks format specification. Schema shows it is an object with start/end, but no description explains ISO 8601 format, timezone handling, or maximum window size. Agents will guess.