Skip to main content
Glama
Sign In
tossinvest-mcp

tossinvest-mcp

by clauzewitz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_prices

Read-onlyIdempotent

Fetch current last-traded prices for up to 200 Korean and US stock symbols in one call.

Instructions

국내·미국 종목의 현재가(최종 체결가)를 한 번에 최대 200개 조회한다.

등락률·기준가는 없다. 전일 대비 등락이 필요하면 get_stock_rankings 를 쓴다.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbols": "<symbols>"
    },
    "name": "get_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolsYes콤마로 구분한 종목 심볼, 최대 200개 (예: 005930,000660,AAPL)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and openWorld, so the safety profile is carried elsewhere; the description adds that the payload contains no change rate and no reference price, which is real behavioral information about the result. It does not say what happens to unknown or delisted symbols or how the 200-item cap is enforced.

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 short sentences and a line break, with the core capability front-loaded and the alternative routed second. No filler or repetition.

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?

For a single-parameter read tool with no output schema, the description conveys what value is returned and what is deliberately absent. A brief note on response shape (symbol-to-price mapping) or handling of missing symbols would close the remaining gap.

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% and there is only one parameter, whose comma-separated format and 200-symbol cap are fully documented in the schema. The description restates the 200 limit without adding syntax, error, or ordering semantics beyond the schema, so 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?

The description gives a specific verb and resource (look up current / last-traded price) plus scope (Korean and US symbols, up to 200 at a time). It explicitly defines what the value is — final execution price — which distinguishes it from quote-style siblings such as get_orderbook and get_candles.

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?

It states a clear exclusion condition and names the alternative tool: if you need day-over-day change, use get_stock_rankings. It does not address other near-neighbors (get_orderbook, get_recent_trades, get_candles), so the routing is clear for one case but not exhaustive.

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