Generate a mock collection JSON by providing a collection name and endpoints list. Define newline-separated method and path pairs to structure mock API responses.
Generate a mock collection JSON.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Collection name | |
| endpoints | Yes | Newline method path |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Generate' and does not reveal side effects, output behavior, required input format, or whether the operation has any state-changing consequences.
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 short sentence with no filler or redundancy. It is concise and front-loaded, though it is so sparse that some context is left implicit.
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?
With no annotations and no output schema, the description should explain more about how to invoke the tool correctly. It does not clarify the endpoints string format beyond the schema's terse 'Newline method path', nor what the generated JSON will look like.
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%, with both 'name' and 'endpoints' already described in the input schema. The description adds no extra parameter meaning, so it stays at the baseline score.
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 ('Generate') and resource ('mock collection JSON'), so an agent knows what the tool produces. However, it does not distinguish this from the sibling tools apimock_mock and apimock_status, and the exact meaning of 'mock collection JSON' is somewhat ambiguous.
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?
The description gives no guidance on when to use this tool instead of apimock_mock or apimock_status. There are no explicit use cases, exclusions, or alternative routing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.