Skip to main content
Glama
konstantinmk

market-mcp

by konstantinmk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_candles

Read-onlyIdempotent

Retrieve historical OHLCV candles from Moscow Exchange and T-Invest for any ticker, from 1-minute to monthly intervals. Supports pagination and date ranges for price analysis and charting.

Instructions

Исторические свечи OHLCV от 1 минуты до месяца — для динамики цены, доходности за период, графиков.

    Дневные, недельные и месячные свечи берутся с MOEX ISS без ограничения глубины;
    внутридневные — из T-Invest, если есть токен. По умолчанию: день — последний год, внутри дня — сутки.
    За один вызов не больше 1000 свечей: при next_cursor повтори запрос с cursor.
    Время: дата YYYY-MM-DD для day/week/month, иначе UTC ISO 8601.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boardNoРежим торгов (class code): TQBR, TQCB, TQOB, TQTF, CETS, SPBFUT. Нужен только если тикер неоднозначен.
cursorNonext_cursor из предыдущего ответа для следующей страницы.
tickerYesТикер или SECID: SBER, SU26238RMFS4, CNYRUB_TOM, IMOEX.
date_toNoКонец периода включительно: YYYY-MM-DD или ISO 8601. По умолчанию — сейчас.
intervalNoИнтервал свечи.day
date_fromNoНачало периода: YYYY-MM-DD (дата торгов, МСК) или ISO 8601 в UTC.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already mark this as read-only and idempotent, and the description adds substantial operational behavior beyond that: data source differences (MOEX ISS vs T-Invest), the 1000-candle pagination limit, default time ranges, and interval-specific date formats. This is exactly the kind of contextual behavior an agent needs.

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?

Every sentence earns its place: purpose first, then source behavior, pagination, and time conventions. The formatting is scannable and free of filler.

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

Completeness5/5

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

For a moderately complex tool with six parameters, the description covers all operationally critical details: intervals, data sources, token dependency, pagination, defaults, and date formatting. Since an output schema exists, return-value details are not required, and nothing essential for calling the tool correctly is missing.

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 description coverage is 100%, so the schema already documents each parameter. The description adds valuable semantic context on top: default periods, the meaning of next_cursor for pagination, and the YYYY-MM-DD vs ISO 8601 distinction based on interval. This goes beyond the baseline without replacing 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 opens with a specific verb and resource: 'Исторические свечи OHLCV' (historical OHLCV candles) with a clear interval range from 1 minute to month. It also states concrete use cases — price dynamics, period returns, charts — and the 'historical' framing distinguishes it from sibling tools like get_quote.

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

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear context for when to use the tool: for price dynamics, period returns, and charts requiring historical candles. It does not explicitly name sibling alternatives or state when not to use it, so it falls short of a full 5, but the use-case framing is strong.

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