cancel_all_orders
Cancel all open orders on Kraken to clear pending trades in one action.
Instructions
Cancel every open order.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Cancel all open orders on Kraken to clear pending trades in one action.
Cancel every open order.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must disclose all behavioral traits. It only says 'cancel every open order,' omitting details like irreversibility, scope across markets, or impact on order book.
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?
Single sentence with no extraneous words. Efficient and front-loaded.
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?
Despite low complexity, the description lacks behavioral context for a destructive action. No mention of idempotency, confirmation, or whether it cancels orders across all trading pairs.
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?
Input schema has zero parameters, so the description adds no parameter info. Baseline for 0 parameters is 4, as schema coverage is inherently 100%.
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 clearly states 'Cancel every open order,' using a specific verb and resource. It effectively distinguishes from sibling tools like cancel_order and cancel_all_orders_after.
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 on when to use this tool versus alternatives (e.g., cancel_order for a single order). Lacks any mention of context or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/XavierBeheydt/mcp-kraken'
If you have feedback or need assistance with the MCP directory API, please join our Discord server