moex-mcp

get_candles

Retrieve OHLCV candlestick data for a security on Moscow Exchange. Specify ticker, interval (daily, hourly, or minute), and optional date range to obtain price history for analysis.

Instructions

Get OHLCV candlestick data for a security. Use interval=24 for daily candles, 60 for hourly, 10 or 1 for minutes.

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": {
      "security": "<security>",
      "interval": "<interval>"
    },
    "name": "get_candles"
  }
}

Input Schema

Name	Required	Description	Default
`from`	No	Start date (YYYY-MM-DD)
`till`	No	End date (YYYY-MM-DD)
`board`	No	Trading board (e.g. 'TQBR')
`engine`	No	Trading engine (default 'stock')	stock
`market`	No	Market (default 'shares')	shares
`interval`	Yes	Candle interval in minutes: 1, 10, 60, or 24 (daily). Use 24 for day candles
`security`	Yes	Security ticker (e.g. 'SBER')

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 30, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description carries the behavioral burden. It does disclose the read-only nature and OHLCV output shape, but it does not mention default date range behavior, timezone, ordering, pagination, or response format. This is acceptable but has clear gaps.

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?

Two short sentences with no filler; the main purpose is front-loaded and the interval guidance is compact.

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

Completeness3/5

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

Adequate for a simple read tool, since the schema documents all parameters and required fields. However, with no output schema and multiple overlapping sibling tools, the description leaves out defaults for from/till, response shape, and when to prefer this tool over similar history/candles tools.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds value by mapping interval values to calendar units ('24 for daily, 60 for hourly, 10 or 1 for minutes'), going slightly beyond the schema's generic 'minutes' wording.

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?

States a specific action and object: 'Get OHLCV candlestick data for a security.' This clearly identifies the data type and resource, and the interval sentence clarifies the granularity options. It does not explicitly distinguish it from siblings like get_history or get_historical_candles, so it stops short of a 5.

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 on when to choose this tool over sibling tools such as get_historical_candles or get_history. The 'Use interval=...' sentence is parameter-level advice, not tool-selection guidance, and no exclusions or alternatives are mentioned.

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