Skip to main content
Glama
tossinvest-mcp

tossinvest-mcp

by clauzewitz

get_credit_trading

Read-onlyIdempotent

Retrieve daily credit trading data for a Korean stock, including new, repayment, and balance figures for margin loans and short selling, plus balance ratios and T+1 updates.

Instructions

[국내 전용] 종목의 일별 신용거래(신용융자·신용대주) 신규·상환·잔고.

잔고 비율·공여율 포함. T+1 에 반영된다.

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

Input Schema

NameRequiredDescriptionDefault
countNo조회 일수 (최대 100)
untilNo이 날짜(YYYY-MM-DD, 포함)까지 최신순으로 조회. 다음 페이지는 이전 응답의 nextUntil 값을 넣는다
symbolYes국내 종목 6자리 코드(예: 005930). 미국 종목은 지원하지 않는다

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/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 and the description is not obligated to restate it. What it does add is genuinely useful and non-redundant: the T+1 settlement lag tells the agent the latest data point will not be current-day, which affects expectations about recency and caching. It does not discuss history depth limits or rate limits, keeping it short of a 5.

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: scope tag, payload contents, and freshness caveat. The scope restriction is front-loaded, nothing is repeated, and the included-field list is compact rather than prose.

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?

There is no output schema, so the description must convey what comes back; it does so by naming the metric families (new, repayment, balance, balance ratio, loan-to-value ratio). Combined with full parameter documentation in the schema and safety annotations, this is close to sufficient, with the only gap being the shape/granularity of the returned series.

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 every parameter (symbol, count, until with its nextUntil pagination hint) is documented in the schema itself. The description adds no parameter-level guidance at all — it never mentions the day-count limit or the pagination cursor — so this sits at the baseline where the schema carries the load.

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-resource pair (daily credit trading for a symbol) and enumerates the sub-metrics it returns: 신용융자/신용대주 신규·상환·잔고, 잔고 비율, 공여율. The '[국내 전용]' tag and the schema's 'US stocks not supported' both bound the scope, which separates it from generic siblings like get_stock_info or get_prices, though it never names an adjacent tool such as get_short_selling or get_securities_lending that an agent might confuse it with.

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 tool for credit-loan/short-margin flow data on Korean symbols. The '[국내 전용]' restriction functions as an exclusion (do not call for US symbols), but there is no explicit statement of when to pick this over get_short_selling, get_securities_lending, or get_investor_trading, which cover overlapping market-flow topics.

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