Coding PROMPT
MCP Server Design Review
July 26, 2026Optimized for: anyMCP server quality review
Review this MCP server design before it ships. You are looking for the failure modes that only appear once an agent is driving it, not a human. Check each of these and report concretely: 1. TOOL NAMING: are names unambiguous to a model that only sees the name and description? Flag any pair a model could confuse. 2. DESCRIPTIONS: does each description say when NOT to use the tool? Missing negative guidance is the top cause of wrong tool selection. 3. PARAMETER SCHEMAS: are required and optional correct? Any parameter a model will have to guess at? 4. ERROR MESSAGES: does a failure tell the model what to do differently, or just that something broke? 5. RESPONSE SIZE: which tool can return an unbounded payload and blow out the context window? Every one of them needs a limit. 6. DESTRUCTIVE OPERATIONS: which calls are irreversible, and is that obvious from the description alone? 7. IDEMPOTENCY: what happens if the agent retries after a timeout that actually succeeded? For each finding: severity, the concrete failure scenario, and the fix. Server definition: [PASTE TOOL DEFINITIONS]
Reviews an MCP server for the failure modes that only show up under agent control: ambiguous names, unbounded payloads, unsafe retries.
Submit your own AI prompts to the community. The best ones get featured on TokenCalculator - and credited to you.