cancel_withdrawal
Cancel a pending withdrawal on Kraken by specifying the asset and reference ID to stop the transaction.
Instructions
Request cancellation of a pending withdrawal.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| asset | Yes | ||
| refid | Yes |
Cancel a pending withdrawal on Kraken by specifying the asset and reference ID to stop the transaction.
Request cancellation of a pending withdrawal.
| Name | Required | Description | Default |
|---|---|---|---|
| asset | Yes | ||
| refid | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden for behavioral disclosure. It only states 'Request cancellation' without specifying whether cancellation is immediate, requires special permissions, or any side effects.
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 extremely concise but under-specified; it does not provide enough value for an agent to use the tool correctly, so it is not appropriately sized.
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?
The tool is simple but the description omits parameter details and behavioral context, leaving gaps in completeness for an AI agent.
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 0%, and the description does not explain the meaning or usage of parameters 'asset' and 'refid', failing to compensate for the gap.
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 the action (cancel) and the target (a pending withdrawal), differentiating it from order cancellation tools among siblings. However, it does not explicitly mention that the cancellation is for a specific withdrawal identified by refid.
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 alternatives like cancel_order or account_transfer, nor are prerequisites (e.g., withdrawal must be in pending state) mentioned.
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