tossinvest-mcp

Get index and bond yield prices

tossinvest_get_market_indicator_prices

Read-onlyIdempotent

Fetch current Korean market index levels (KOSPI, KOSDAQ) and treasury bond yields (2Y-30Y) as price data. Specify comma-separated symbols to get last price and timestamp.

Instructions

Get the current level of Korean market indices and treasury yields.

Supported symbols (this catalog and nothing else):

KOSPI, KOSDAQ — index level in points
KR_BOND_2Y, KR_BOND_3Y, KR_BOND_5Y, KR_BOND_10Y, KR_BOND_20Y, KR_BOND_30Y — yield in percent ('3.25' means 3.25%)

Args:

symbols (string): Comma-separated catalog symbols, e.g. 'KOSPI,KOSDAQ'.
response_format ('markdown' | 'json'): default 'markdown'.

Returns { count, prices: [{ symbol, lastPrice, timestamp }] }.

For individual stocks use tossinvest_get_prices — this endpoint rejects stock symbols.

Errors: 400 unsupported-symbol for anything outside the catalog.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`symbols`	Yes	Comma-separated catalog symbols, e.g. 'KOSPI,KOSDAQ' or 'KR_BOND_3Y,KR_BOND_10Y'.
`response_format`	No	Output format: 'markdown' for a compact human-readable summary, 'json' for the complete raw payload.	markdown

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes
`prices`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 8, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already mark the tool as read-only, idempotent, and non-destructive, so the description only needs to add behavior beyond that. It does: it discloses the closed symbol catalog, the meaning of yield values in percent, the exact return shape, and the 400 unsupported-symbol error. No contradiction with annotations.

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?

The description is well structured with clear sections for supported symbols, args, return value, sibling routing, and errors. Every sentence adds information, and the most important scoping detail is front-loaded.

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 read-only data-fetching tool, the definition is complete: it fully specifies symbols, units, return shape, error behavior, and the alternative for stock symbols. Given the annotations and output schema, no critical operational detail 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 coverage is 100%, so the schema already documents both parameters. The description adds meaningful extra context by enumerating the accepted symbol catalog, clarifying units (points vs. percent yields), and giving explicit usage examples for response_format. This raises it above the baseline 3.

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: getting the current level of Korean market indices and treasury yields. It also names the exact supported symbols and contrasts itself with tossinvest_get_prices, making its purpose unmistakable among many sibling tools.

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

Usage Guidelines5/5

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

The description explicitly states the tool's supported catalog and says 'For individual stocks use tossinvest_get_prices — this endpoint rejects stock symbols.' This gives clear when-to-use and when-not-to-use guidance with a named alternative.

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

Deploy Server