Skip to main content
Glama
tossinvest-mcp

tossinvest-mcp

by scjang01

대차거래 동향 조회

toss_get_stock_securities_lending
Read-only

Retrieve daily institutional securities lending data for Korean stocks, including execution, repayment, and balance in quantity and KRW, with pagination via the until parameter.

Instructions

국내 종목의 기관 간 일별 대차 체결·상환·잔고(수량·KRW). 신용대주와 별개. 다음 페이지: 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_securities_lending"
  }
}

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

B3.4/5.0
Behavior4/5

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

The annotations already declare readOnly=true, destructive=false and openWorld=true, so safety is covered. The description still adds real behavior beyond them: the data is daily, institutional-only, denominated in both shares and KRW, and paged. The pagination hint 'nextUntil → until' is a genuinely useful operational detail that tells the agent how to continue past the first page. It loses a point because it doesn't say whether the history is bounded or how far back data goes.

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?

Three short fragments with the resource and scope front-loaded, then the exclusion, then the pagination rule. Nothing is wasted, though the telegraphic fragment style and the unexplained shorthand 'nextUntil' slightly reduce first-read clarity.

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 three-parameter read-only lookup with no output schema, the description covers the data domain, units and pagination, which is the core of what an agent needs. It is still incomplete on what `count` does, that `symbol` is a Korean ticker, and what fields come back in the balance object, leaving meaningful gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description has to carry all parameter meaning, and it only explains the `until` cursor through the pagination hint. `symbol` is never described as a domestic ticker despite the pattern, and `count` (1–100 page size) is not mentioned at all. The schema therefore leaves two of three parameters semantically opaque.

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 definition names a specific resource and measurement set: daily securities lending executions, repayments and balances (quantity and KRW) for domestic stocks. Adding '기관 간' (institutional-only) narrows the scope, and '신용대주와 별개' separates it from the credit-loan concept covered by the sibling credit-trades tool. It stops just short of a 5 because the description never states that this is a query and not an aggregate or ranking view.

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?

The exclusion '신용대주와 별개' implies that an agent wanting margin/credit lending data should look elsewhere, which is useful disambiguation. However, it never names a sibling tool or says explicitly when this tool is the right choice versus short-selling, program-trading, or credit-trade tools. The guidance is only implied and depends on the agent knowing the sibling catalog.

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