get_tradable_pairsRetrieve all tradable asset pairs on Kraken Pro, including fees, leverage, and limits. Filter by a specific pair such as XBTUSD or omit it to list every market.
Get all tradable asset pairs on Kraken with fees, leverage, and limits
| Name | Required | Description | Default |
|---|---|---|---|
| pair | No | Specific pair to filter (e.g., XBTUSD), or leave empty for all pairs |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It doesn't state whether the call is read-only, whether results are cached, how pagination works, or how the optional pair filter changes the response, leaving behavioral gaps for a no-annotation tool.
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?
A single, front-loaded sentence with zero filler. The verb, resource, and returned fields are all stated immediately.
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 simple single-parameter read tool with no output schema this is minimally viable. However, with no annotations it could add more value by describing response shape, filtering behavior, or required permissions.
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 100%, so the single optional pair parameter is fully documented in the schema, establishing a baseline of 3. The description adds no syntax or format guidance beyond what the schema already provides.
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?
Clear verb+resource: 'Get all tradable asset pairs on Kraken', with the data returned (fees, leverage, limits) stated. It distinguishes itself from market-data siblings like get_ticker or get_order_book, though it doesn't name them explicitly.
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 when-to-use or when-not-to-use guidance. It doesn't say to call this before placing orders or retrieving pair metadata, nor does it differentiate from sibling lookup tools such as get_asset_info.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.