Skip to main content
Glama
GodPrompt MCP Server

GodPrompt MCP Server

Review supplied MCP contracts

review_mcp_tool_contracts
Read-onlyIdempotent

Audit MCP tool descriptions, input/output schemas, and annotations with a read-only, bounded design review to catch contract clarity and consistency issues before use.

Instructions

Read-only bounded design audit of MCP tool descriptions, input/output schemas and annotations. Not a protocol validator, vulnerability scanner or permission grant.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tools": "<tools>"
    },
    "name": "review_mcp_tool_contracts"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolsYes

Output Schema

NameRequiredDescriptionDefault
issuesYes
statusYes
warningYes
truncatedYes
reviewed_toolsYes
independently_verifiedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.4.2

TDQS

A3.8/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, idempotent, destructive=false and openWorld=false, so safety is covered structurally. The description adds scope framing ('bounded', 'design audit' versus runtime validation) but says nothing about how deep the audit goes, what happens to oversized input beyond the schema's maxItems of 40, or what the audit produces.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero waste, with the core purpose front-loaded and the exclusions compressed into a single clause. Nothing could be removed without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described, and the input constraints live in the schema. For an audit tool the description is nearly sufficient, with the remaining gap being what kind of findings the audit yields and any depth or effort expectations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate; it partially does by naming the three things to supply (descriptions, input/output schemas, annotations), which maps onto the nested properties of the single 'tools' array. It adds no guidance on how to batch or scope the up-to-40 tools, leaving the parameter largely explained only by the schema itself.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: a 'read-only bounded design audit of MCP tool descriptions, input/output schemas and annotations.' The target artifact (MCP contracts) is clear enough to distinguish it from audit_agent_instructions or review_code_change, though it does not name a sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit exclusions — 'Not a protocol validator, vulnerability scanner or permission grant' — which is real negative routing guidance an agent can act on. It stops short of positive when-to-use guidance or naming the alternative tool an agent should pick instead, so it is strong but not complete.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.