Skip to main content
Glama
Sign In
tossinvest-mcp

tossinvest-mcp

by clauzewitz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_orderbook

Read-onlyIdempotent

Retrieve bid and ask prices with remaining quantities for Korean and US stocks, including integrated KRX+NXT order books for domestic symbols.

Instructions

종목의 매수·매도 호가와 잔량을 조회한다. 국내는 KRX+NXT 통합 호가.

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": {
      "symbol": "<symbol>"
    },
    "name": "get_orderbook"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYes종목 심볼. 국내는 6자리 종목코드(예: 005930), 미국은 티커(예: AAPL)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/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 covered. The description adds useful data-source context (KRX+NXT consolidated quotes for domestic symbols) but says nothing about whether this is a snapshot or streaming, how many depth levels are returned, or latency/refresh characteristics.

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

Conciseness4/5

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

Two short sentences, front-loaded with the purpose and followed by the scope caveat; nothing is wasted. The second sentence is terse enough that its implication (integrated feed vs single exchange) takes a moment to parse.

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?

With no output schema, the description carries the burden of describing what comes back, and it only hints at quote prices plus remaining quantities without specifying depth levels, ordering, or units. It is adequate for identifying the tool but thin for interpreting its response.

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 the single symbol parameter already documents domestic 6-digit codes and US tickers. The description adds no further parameter meaning, so the baseline of 3 applies.

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 a specific verb and resource (retrieve bid/ask quotes and remaining quantities for a symbol) and adds a scope note that domestic quotes are KRX+NXT integrated. This clearly separates it from get_prices and get_recent_trades by resource, though it never names those siblings.

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 resource name: an agent can infer this is for depth/orderbook data rather than trades or candles. There is no explicit when-to-use or when-not-to-use guidance and no alternative tool is mentioned.

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