Skip to main content
Glama
Kirillov808

moex-iss

by Kirillov808
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

moex_zcyc

Read-only

Retrieve the OFZ zero-coupon yield curve (G-curve) for a specific date, returning annual yields, parameters, and securities. Query Moscow Exchange ISS data without an API key.

Instructions

Кривая бескупонной доходности ОФЗ (G-curve) на дату: yearyields (period лет -> value %), params, securities.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoДата YYYY-MM-DD (время MSK; для свечей можно 'YYYY-MM-DD HH:MM:SS').
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

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds the returned shape (yearyields/params/securities) and date basis, but omits authentication, rate limits, and behavior when date is omitted.

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

Conciseness3/5

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

It is a single telegraphic sentence with the resource front-loaded. The colon-separated output hints make it feel fragmentary rather than fully structured for quick parsing.

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?

No output schema exists, so the description must carry return context. It names three output sections but does not explain their structure, and usage/prerequisite context is absent, leaving meaningful gaps.

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 coverage is 100%, so all five parameters are documented in the schema. The description only echoes the date concept and output field mapping; it adds no parameter-level meaning beyond the schema.

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 the specific resource: zero-coupon OFZ yield curve (G-curve) and date scope. It does not differentiate from sibling endpoints such as moex_bond_yields_history or moex_history, but the resource itself is unambiguous.

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 over moex_bond_yields_history or other yield-curve tools. There are no usage conditions, exclusions, or prerequisites.

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