Skip to main content
Glama
Sign In
tossinvest-mcp

tossinvest-mcp

by clauzewitz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_price_limits

Read-onlyIdempotent

Fetch the current trading day's upper and lower price limits for a Korean or US stock symbol to verify allowed order prices.

Instructions

종목의 당일 상한가·하한가를 조회한다.

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

Input Schema

NameRequiredDescriptionDefault
symbolYes종목 심볼. 국내는 6자리 종목코드(예: 005930), 미국은 티커(예: 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 elsewhere. The description adds only the temporal qualifier 당일, implying the limits are computed per trading day rather than static, but says nothing about real-time refresh, market-hours behavior, or what happens for instruments without daily limits. Against the lowered bar set by annotations, this is adequate but thin.

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?

A single front-loaded sentence with no filler and no restatement of the tool name. Nothing in it fails to earn its place.

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?

For a one-parameter read tool with full schema coverage and annotations, the core is covered. However, the schema explicitly admits US tickers while the description restricts the concept to 당일 상한가·하한가, leaving unresolved whether limits are returned for markets without daily price bands.

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 coverage is 100%: the single symbol parameter already documents the 6-digit Korean code vs. US ticker format and carries a pattern constraint. The description adds no meaning beyond the schema, 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?

The description names a specific verb (조회한다 / retrieves) and a specific resource (당일 상한가·하한가 / today's upper and lower price limits), which is distinct from the price data returned by the sibling get_prices or get_candles. It does not explicitly contrast itself with those siblings, though the narrow resource makes misuse unlikely.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternatives are named. Usage is only implied by the narrow resource, but for a single-symbol read lookup this is largely self-evident.

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