MCP server for Honeybadger error tracking service
Three tools with clear verb-noun naming (find_project, search_faults, get_backtrace) and documented descriptions. All tools have input schemas with type definitions and parameter descriptions. However, output schemas are not documented, LLMs cannot predict return structure. Parameter descriptions lack format constraints (e.g., 'nameOrId' accepts string but doesn't clarify if it's numeric ID or project name). Error handling is minimal, no recovery guidance or actionable error messages visible in tool implementations. Tool descriptions are adequate (50-100 chars) but lack dependency hints or prerequisites. No tool annotations (readOnlyHint, etc.) despite all being read-only operations.
Find a Honeybadger project by name or ID
Get the backtrace for a specific fault
Search for faults in a Honeybadger project
Output schemas not documented. LLMs cannot predict return structure (fields, types, nesting). Breaks downstream tool chaining and forces agents to guess field names.
Parameter 'nameOrId' in find_project lacks format guidance. Ambiguous whether to pass '123' (numeric ID) or 'MyProject' (name). Description should clarify: 'Project ID (numeric) or name (string)'.
No error handling guidance visible. Tools lack recovery hints (e.g., 'Project not found. Try search_faults() with partial name'). Agents cannot self-correct on failures.
Tool annotations missing. All three tools are read-only but lack readOnlyHint annotation. Agents cannot distinguish safe tools from destructive ones without explicit hints.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 52 | 2026-07-28+ | v2 |
search_faults 'query' parameter description includes example ('is:unresolved environment:production') but no formal grammar or enum. LLMs may hallucinate invalid query syntax.