Generates a mock response for an endpoint by specifying HTTP method, path, and optional schema. Enables API testing without a live backend.
Generate a mock response for an endpoint.
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | Path | |
| method | Yes | HTTP method | |
| schema | No | Optional schema/fields |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description bears full responsibility for disclosing behavior. It only says 'generate a mock response,' which suggests a read-like operation but does not clarify side effects, required authentication, or what exactly 'mock' entails. This is insufficient for an unannotated tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence without filler. It front-loads the core action, though it may be overly terse given the lack of other supporting information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with no output schema and no annotations, the description is too shallow. It should clarify what 'mock response' means (e.g., returns synthetic data), acceptable methods like GET/POST, and any constraints on path format, so an agent can invoke it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already documents each parameter (path, method, schema). The description itself adds no further semantic detail beyond what the schema states, meeting the baseline.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a clear verb and resource: 'Generate a mock response for an endpoint.' It implies the tool's primary function and is distinguishable from siblings like apimock_status and apimock_collection, though it does not explicitly differentiate them.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus the siblings. There is no mention of alternatives, prerequisites, or typical use cases, leaving the agent to infer context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.