Skip to main content
Glama
tossinvest-mcp

tossinvest-mcp

by scjang01

프로그램매매 동향 조회

toss_get_stock_program_trades
Read-only

Fetch daily arbitrage and non-arbitrage program trading volumes (buy, sell, net shares) for Korean stocks from KRX; supports pagination for historical data.

Instructions

국내 종목의 차익·비차익 프로그램 일별 매수·매도·순매수 거래량(주). KRX만 집계하며 당일은 변동 가능. 다음 페이지: nextUntil → until.

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

Input Schema

NameRequiredDescriptionDefault
countNo
untilNo
symbolYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.2
    • removedInput schema / properties / until / pattern
      Removed value: -"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$"
  2. Addedv0.3.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=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds real behavioral context on top: KRX is the sole aggregation source, current-day values may still change, and pagination continues via the nextUntil value. It does not describe result size limits or response shape, so this is useful but not rich.

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 compact clauses: what is returned, the coverage/volatility caveat, and the pagination rule. Nothing is redundant and the core purpose is front-loaded before the caveats.

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 three-parameter read-only tool with no output schema, the definition covers the returned metrics, market scope, freshness caveat, and pagination loop. The remaining gap is that symbol format and the count bound are undocumented anywhere, since the schema supplies no descriptions.

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?

With 0% schema description coverage, the description must carry the burden, and it does explain the non-obvious 'until' parameter as the pagination cursor carried over from a previous response's nextUntil. 'symbol' and 'count' are left unexplained (no format hint, no max of 100 noted), so coverage is partial rather than complete.

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 resource and scope: daily arbitrage/non-arbitrage program-trading buy, sell, and net-buy volume (in shares) for a domestic stock. That is enough to distinguish it from siblings like investor trading, credit trades, or short selling. It does not explicitly name an alternative tool, which keeps it just short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit statement of when to use this versus the many adjacent flows (investor trading, credit trades, short selling) or of prerequisites. The KRX-only note implies a market-scope condition, but that is a data caveat rather than routing guidance. An agent must infer the choice from the tool name alone.

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