Skip to main content
Glama
konstantinmk

market-mcp

by konstantinmk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

screen_market

Read-onlyIdempotent

Screen Moscow Exchange instruments by filters like liquidity, price change, yield, or capitalization, then sort results to find top movers, liquid stocks, or high-yield OFZs.

Instructions

Скринер всех бумаг режима торгов Мосбиржи с фильтрами и сортировкой.

    Для вопросов «самые ликвидные акции», «кто сильнее всех упал сегодня», «ОФЗ с доходностью выше 15%».
    Строки: secid, name, price, change_pct, volume, value_rub, capitalization; для облигаций ещё
    yield_pct, duration_days, maturity. Данные ISS с задержкой 15 минут. Не больше 500 строк за вызов.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoПоле сортировки.value_rub
boardNoРежим торгов: TQBR — акции, TQTF — фонды, TQCB — корп. облигации, TQOB — ОФЗ, CETS — валюта, RFUD — фьючерсы.TQBR
limitNo
orderNodesc
cursorNonext_cursor из предыдущего ответа для следующей страницы.
filtersNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

The description adds behavioral context beyond the annotations: it discloses the 15-minute data delay from ISS, the maximum of 500 rows per call, and the specific output columns for stocks vs bonds. This complements the readOnlyHint/openWorldHint annotations without contradicting them. It does not explain pagination behavior, but the schema already covers the cursor parameter.

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

Conciseness4/5

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

The description is concise: three sentences, front-loaded with purpose, followed by example use cases and key constraints. It earns its place with essential info, though it could be slightly more structured to separate purpose, output, and limits.

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

Completeness4/5

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

Given the tool's moderate complexity (6 top-level params, nested filter object, output schema), the description provides key context: output columns, delay, row limit, and example scenarios. It covers most operational essentials, but the weak parameter semantics leave some gaps for an agent trying to craft precise filters without opening the schema.

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

Parameters2/5

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

Schema description coverage is only 50%, so the description needs to compensate for undocumented parameters like max_price, min_price, max_yield_pct, max_change_pct, limit, and order. The description only generically mentions 'filters and sorting' and lists output fields; it does not clarify units, inclusion of boundaries, or how these parameters behave. The schema's own descriptions cover some, but the main description adds little param-level value.

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 states a specific verb ('screener of all securities'), the resource (Moscow Exchange trading modes), and gives concrete example questions ('most liquid stocks', 'OFZ with yield above 15%') that clearly distinguish it from sibling tools like get_quote or get_candles. The purpose is unambiguous and immediately understandable.

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 provides clear usage context through example questions, implying when to use the tool for market-wide screening rather than single-instrument queries. It does not explicitly name sibling alternatives or state when not to use it, so it stops short of full when/when-not guidance.

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