Skip to main content
Glama
Sign In
mcp-kraken

mcp-kraken

by XavierBeheydt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_ohlc

Retrieve OHLC (Open, High, Low, Close) candle data for any trading pair on Kraken. Specify interval and optional start time to filter results.

Instructions

Return OHLC candles.

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": {
      "pair": "<pair>"
    },
    "name": "get_ohlc"
  }
}

Input Schema

NameRequiredDescriptionDefault
pairYesTrading pair (e.g. `XBTUSD`).
intervalNoCandle width in minutes — one of `1, 5, 15, 30, 60, 240, 1440, 10080, 21600`.
sinceNoUnix timestamp; return candles after this.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only says 'Return OHLC candles' without mentioning caching, rate limits, data source, timeframe limits, or whether results are paginated. This leaves significant gaps for the agent.

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

Conciseness2/5

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

The description is only three words, which is under-specified. While concise, it sacrifices completeness and does not earn its place with valuable information beyond the tool name.

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?

Given no output schema, the description should detail what the candles contain (open, high, low, close, volume, etc.). It fails to do so. The tool is simple but the description is insufficient for an agent to understand the return format.

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 description coverage is 100%, so the input schema already explains each parameter. The description adds no extra meaning beyond the schema, making it adequate but not better.

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

Purpose4/5

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

The description 'Return OHLC candles' clearly states the tool returns Open-High-Low-Close candle data, using a specific verb and resource. It is distinct from sibling tools like get_ticker or get_order_book, though it could elaborate on the exact fields returned.

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?

The description provides no guidance on when to use this tool versus alternatives such as get_recent_trades or get_ticker. No context about prerequisites, typical use cases, or exclusions is given.

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