Skip to main content
Glama
toss-invest-mcp

toss-invest-mcp

by jihwan0102

kr_market

Read-only

Retrieves current prices for KOSPI, KOSDAQ, and Korean government bond yields from 2Y to 30Y. Use it to check Korean market levels and interest rates.

Instructions

국내 지수/국채 금리 현재가. 지원: KOSPI, KOSDAQ, KR_BOND_2Y/3Y/5Y/10Y/20Y/30Y.

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": "kr_market"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolsNoKOSPI,KOSDAQ,KR_BOND_3Y,KR_BOND_10Y

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already declare a safe read-only, open-world, non-destructive operation. The description adds that the tool returns current prices for Korean indices and government bond yields, but it does not disclose freshness, rate limits, or error behavior, so it adds only modest behavioral context.

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 compact sentences front-load the resource and then immediately list supported values. There is no redundant or filler text, and every token helps the agent choose valid symbols.

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?

This is a simple one-parameter read-only tool with an output schema and safety annotations already covering the return and safety profile. The description supplies the valid symbol universe, so it is essentially complete; the only minor gap is explicit multi-symbol input syntax.

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 0% and there are no enums, so the description must carry the parameter semantics. It does so by enumerating all supported symbols, including KOSPI, KOSDAQ, and the KR_BOND tenors. It does not explicitly state the comma-separated multi-symbol format or the default, though the schema default implies the format, so it falls slightly short of full compensation.

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?

It states a specific resource (Korean index and government bond yields) and a current-price retrieval purpose, and it enumerates the supported symbols. It does not explicitly distinguish itself from siblings such as quote or stock_info, so it is clear but lacks full sibling differentiation.

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

Usage Guidelines3/5

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

The supported-symbol list implies that this tool is for Korean index and bond-yield quotes, but the description gives no explicit when-to-use guidance, no exclusions, and no guidance for choosing between this and quote or stock_info. Usage is therefore inferable but not spelled out.

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