Skip to main content
Glama
tossinvest-mcp

tossinvest-mcp

by clauzewitz

get_stock_info

Read-onlyIdempotent

Retrieve basic stock information for up to 200 comma-separated symbols, including name, market, currency, listing status, and trading halt status.

Instructions

종목 기본 정보를 최대 200개 조회한다.

이름, 시장, 통화, 상장 상태, 거래정지 여부 등을 담는다.

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_stock_info"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds the field set returned and reinforces the 200-symbol ceiling, but says nothing about behavior for unknown/delisted symbols, partial results, or ordering of the response — gaps that matter for a batch lookup.

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 action and scope, followed by the return contents — no wasted wording. The repeated 200-symbol cap is minor redundancy with the schema.

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?

With one fully documented parameter and no output schema, the description's field enumeration does the work an output schema would otherwise do. Only edge-case behavior (invalid symbols, delisted entries, response ordering) is left unstated.

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 parameter is already documented with format, pattern, cap, and an example (005930,000660,AAPL). The description only repeats the 200 limit, adding no new meaning beyond the schema, so the baseline 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?

The description states a specific verb (조회한다) and resource (종목 기본 정보) plus the batch cap, and enumerates the returned fields (name, market, currency, listing status, trading-suspension flag). That is enough to distinguish it from price/orderbook/candle siblings, though it never names those siblings explicitly.

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: an agent can infer this is the metadata lookup to call before or alongside get_prices, get_orderbook, or get_stock_warnings, but nothing in the text says when to prefer it or what to call instead. No exclusions or preconditions are given.

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