list_mock_rulesList configured mock rules so you can inspect which requests trigger mocked responses in the capture proxy or standalone mock server.
List configured mock rules. Each rule fires when a matching request flows through either the capture proxy or the standalone mock server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=false, so safety profile is covered. The description adds useful domain context (rules fire via capture proxy or standalone mock server), but does not disclose return shape, ordering, or persistence details.
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?
Two tight sentences, front-loaded with the action, and the second sentence earns its place by explaining the rules' execution context.
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 no-param read-only list tool with no output schema, the description covers what the tool returns conceptually and where rules apply; minor gap is absence of guidance on downstream actions (toggle/update/delete).
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?
Zero parameters, so per the rubric the baseline is 4; description correctly adds no parameter noise and doesn't need to.
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?
States a specific verb (List) and resource (mock rules), and the second sentence explains what a mock rule is and where it applies, distinguishing it from the sibling list_* tools (chaos, rewrite, environments, etc.).
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?
Usage is implied by the 'List configured mock rules' phrasing and its place among list_*/toggle_*/create_mock_rule siblings, but the description doesn't explicitly say when to use this versus e.g. list_chaos_rules or how to follow up with toggle_mock_rule.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.