An MCP server exposing safe, structured analytics tools over a SQLite e-commerce database, with a Claude agent that consumes it.
Server has 6 tools with clear verb-noun naming (list_, describe_, run_, top_, revenue_, create_). All tools have descriptions (10-200 chars, within baseline 34-392 range). Input schemas are present with type declarations. However, parameter descriptions are sparse or missing for several tools (list_tables has empty input; run_query lacks format/safety guidance; create_support_ticket exposes api_key as a parameter, violating secret-injection pattern). Output schemas are not documented. Error handling is minimal, no recovery guidance or actionable error messages visible. The server is READ_ONLY safe except for create_support_ticket, which requires explicit API key validation but lacks confirmation/dry-run pattern.
Open a support ticket for a customer. MUTATION — requires the write API key.
Return the columns (name, type, pk) for a table.
List the tables in the analytics database.
Total revenue and order/customer counts over completed orders.
Run a read-only SQL SELECT/WITH query (single statement, row-capped). Returns {columns, rows, row_count}. Mutating statements are rejected.
Best-selling products by units sold across completed orders.
create_support_ticket exposes api_key as a tool parameter. Credentials must never appear in parameters, use server-side secret injection via environment variables or vault. Agent traces log all parameters, leaking secrets into logs and prompt history.
Output schemas are not documented for any tool. LLMs need to know what fields to expect in responses to plan downstream calls and extract data correctly. Document return types for all tools.
run_query lacks format/safety guidance in parameter description. Should explicitly state: 'A read-only SELECT or WITH query (single statement, max 1000 rows). Mutating statements (INSERT, UPDATE, DELETE, DROP) are rejected.' Current description is vague about constraints.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 57 | 2026-07-28+ | v2 |
list_tables has empty input schema ({}). While correct, the tool description should explain when to call it (e.g., 'Call this first to discover available tables before running queries'). Discovery tools need dependency hints.
create_support_ticket lacks confirmation/dry-run pattern. Irreversible operations (mutations) should support a confirmation step to prevent accidental ticket creation. No error handling visible for invalid customer_id or authorization failures.