Clear all queued response rules without stopping the bridge or resetting received-request history, keeping the default response intact.
Remove all queue_response rules without stopping the bridge or clearing received-request history. The default response (if set) is unaffected.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description fully carries the behavioral burden. It discloses the destructive effect (removes rules) and explicitly states what remains unaffected: the bridge, received-request history, and the default response.
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 main action, and every clause adds distinct information about scope or side effects.
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 parameterless, mutation-only tool with no output schema, the description fully covers what is removed and what is preserved, leaving no practical ambiguity.
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?
Tool has zero parametersholiday, and the schema coverage is 100%, so the baseline is 4; no parameter description is needed.
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?
Uses a specific verb ('Remove') with a clear resource ('all queue_response rules') and immediately distinguishes the operation from bridge lifecycle and request-history tools.
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?
Clearly describes what the tool does and does not do, helping an agent choose it over related tools, though it does not explicitly name alternative tools or list when to prefer them.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.