Skip to main content
Glama
Sign In
tossinvest-mcp

tossinvest-mcp

by clauzewitz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_securities_lending

Read-onlyIdempotent

Fetch daily securities lending records for a Korean stock symbol, covering institutional lending executions, repayments, and outstanding balances over a selected date window.

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

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

B3.4/5.0
Behavior3/5

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

The annotations already establish that this is a read-only, idempotent, open-world operation. The description adds domain context about the data categories covered, but it does not describe pagination behavior, response shape, or any additional operational constraints. With annotations carrying the safety profile, this is adequate 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded sentence with no filler or repetition. The domestic-only constraint and the data categories are packed efficiently. It is terse, but not bloated.

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 simple read-only tool with three fully described parameters and annotations, the description covers the core domain and the domestic restriction. It does not explain the return data beyond naming categories, and it leaves sibling selection implicit. That is enough to call the tool, but not fully complete context.

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%, so the symbol, count, and until parameters are already fully documented in the schema. The description reinforces that the tool is symbol-based and domestic-only, but adds no parameter syntax or semantics beyond the schema. Baseline 3 is appropriate.

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 identifies a specific resource: daily securities lending data (execution, repayment, balance) for a stock. It adds a clear domestic-only scope, which helps distinguish it from broader market or other trading-data siblings. It stops short of a full verb phrase like 'retrieves', but the intended purpose is still clear.

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 '[국내 전용]' marker gives an important usage constraint: this is for Korean stocks only. However, it does not explicitly say when to choose this over related siblings such as get_short_selling or get_credit_trading. Usage is implied but not fully guided.

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