toss-invest-mcp

quote

Read-only

Look up current stock quotes for US tickers or Korean six-digit codes by submitting comma-separated symbols, returning price data for market checks.

Instructions

현재가 조회. symbols 는 콤마 구분 (예: 'AAPL,TSLA' 또는 '005930,000660'). 미국은 티커, 국내는 6자리 코드.

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

Input Schema

Name	Required	Description	Default
`symbols`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 25, 2026

TDQS

A3.5/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is covered without the text. The description adds no behavioral context beyond that — no note on real-time vs delayed data, market coverage limits, batch size limits, or failure behavior for unknown symbols.

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?

Three short sentences, front-loaded with the purpose, then the parameter format. No filler or redundancy; every sentence carries information.

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?

An output schema exists, so return values needn't be explained, and the one required parameter is fully documented including its two input dialects. Minor gaps remain: no cap on the number of comma-separated symbols and no statement about data freshness or exchange prefixes.

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 the single schema field is a bare string, so the description must carry the burden — and it does: comma-separated format, two concrete examples, and the US-ticker vs 6-digit-Korean-code distinction that an agent would otherwise get wrong.

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?

Opens with a specific verb+resource ("현재가 조회" = look up the current price), which unambiguously identifies a quote snapshot. It never names or contrasts sibling tools such as stock_info, candles, or orderbook, so differentiation is left to the reader despite the crowded tool namespace.

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?

Usage is only implied by the verb: it's clear you call this to get a price, but nothing states when to prefer it over stock_info (metadata) or candles/orderbook (history/depth), and no preconditions or exclusions are given.

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

Deploy Server