Skip to main content
Glama
Sign In
moex-iss

moex-iss

by Kirillov808
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

moex_selfcheck

Read-only

Run a 30-second self-check before bulk exports or when ISS data seems inconsistent to verify freshness, route consistency, pagination completeness, accrued interest, and yield.

Instructions

Самопроверка (~30 с): свежесть данных, согласованность роутов, полнота пагинации, пересчёт НКД и доходности. Запускай перед массовой выгрузкой или при сомнениях в данных.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "moex_selfcheck"
  }
}

Input Schema

NameRequiredDescriptionDefault
columnsNoОставить только эти колонки (имена как в ISS, например SECID, LAST).
filenameNoИмя CSV-файла в output/ (иначе генерируется).
save_csvNoВсегда сохранить результат в CSV в output/ (для дальнейшего анализа файла).
max_inline_rowsNoБольше этого числа строк — таблица уходит в CSV (по умолчанию 50).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-network behavior are covered. The description adds meaningful context beyond that: a ~30s runtime estimate and the four diagnostic categories performed, which helps an agent decide whether the cost is worth paying.

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 tight sentences, front-loaded with the action and the diagnostic checklist, followed by the trigger condition. No filler; every clause earns its place.

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?

For a read-only diagnostic with four optional params and no output schema, the description explains what is checked and when to run it, but never says what the result looks like (a pass/fail report, a table, per-check status). Since no output schema exists, that gap falls on the description.

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 four optional params (columns, filename, save_csv, max_inline_rows) are already fully documented in the schema. The description adds nothing about them, so the baseline 3 applies.

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?

States a specific action (Самопроверка) and enumerates exactly what is verified: свежесть данных, согласованность роутов, полнота пагинации, пересчёт НКД и доходности. This clearly distinguishes it from the data-fetching siblings (moex_quote, moex_candles, etc.), which an agent can grasp without opening any schema.

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?

Gives explicit when-to-use guidance: 'Запускай перед массовой выгрузкой или при сомнениях в данных.' Clear triggering conditions, but it names no alternative tool or when-not-to-use case, so it stops short of a 5.

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