Skip to main content
Glama
Sign In
mcp-kraken

mcp-kraken

by XavierBeheydt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_withdrawal_info

Preview withdrawal costs including fees and limits for a given asset and amount on Kraken.

Instructions

Preview withdrawal cost (fee, limits).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "asset": "<asset>",
      "key": "<key>",
      "amount": "<amount>"
    },
    "name": "get_withdrawal_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetYesAsset code.
keyYesWithdrawal-address nickname as registered on Kraken.
amountYesAmount of `asset` to withdraw.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description implies a read-only operation ('Preview'), but without annotations, it should explicitly state that no withdrawal is initiated. It does not disclose any behaviors beyond fee and limits, such as whether the amount parameter affects the preview.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single, front-loaded sentence with no redundant information. Every word contributes to the purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations, the description lacks details on return format, error handling, or behavior when parameters are varied. It is too brief for a tool with three required parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with basic descriptions for each parameter. The description adds general context ('fee, limits') but does not elaborate on how parameters interact or any specific constraints beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Preview withdrawal cost (fee, limits).' The verb 'Preview' and resource 'withdrawal cost' are specific and distinct from sibling tools like 'withdraw' or 'cancel_withdrawal'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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 such as get_withdrawal_status or withdraw. There is no mention of prerequisites or when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools