MCP server for managing support cases and messages with admin API authentication
Three tools with basic schemas and descriptions, but significant gaps in parameter documentation and error handling. Tool names follow verb_noun convention (get_, reply_), which is good. However, parameter descriptions are minimal or absent. No output schemas documented. No error recovery guidance. No tool annotations (readOnlyHint/destructiveHint). The reply_to_support_case tool lacks confirmation/dry-run pattern for a destructive write operation. Overall structure is present but falls short of production quality.
Retrieve all support cases from the system
Retrieve all messages for a specific support case
Send a reply message to a support case as an admin
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields without knowing response structure.
reply_to_support_case (destructive write) lacks confirmation/dry-run pattern. Agents can send unreviewed messages without safeguards.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). LLMs cannot distinguish safe reads from dangerous writes.
get_all_support_cases has no pagination parameters (limit, offset, page_size). Returning all cases risks context window exhaustion.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 41 | 2026-07-28+ | v2 |
Error handling not visible in tool definitions. No recovery guidance, error classification, or actionable error messages documented.