Skip to main content
Glama
tossinvest-mcp

tossinvest-mcp

by clauzewitz

get_short_selling

Read-onlyIdempotent

Retrieve daily short-selling volume, value, and ratio for a Korean stock, with pagination by date; same-day data is finalized in the evening.

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

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 this a read-only, idempotent, open-world call, so the safety profile is covered. The description adds genuinely new behavioral context: the domestic-only data coverage and the data-freshness rule that the current day's figures settle in the evening. It does not describe rate limits or response shape, but for a read tool this is solid added value.

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?

Two short sentences with zero filler: the scope-and-content statement is front-loaded, followed by the single most important freshness caveat. Nothing could be removed without losing information.

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?

With no output schema, the description usefully enumerates the returned metrics (volume, value, ratio), and pagination mechanics are covered in the schema. Only minor gaps remain, such as the exact format or units of returned values, which is acceptable given the schema richness.

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%, with count, until (including pagination via nextUntil), and symbol all documented in the schema itself. The description adds no additional meaning about these parameters, 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 the specific resource (daily short-selling volume, trading value, and short-selling ratio for a stock) and scopes it to domestic listings, which distinguishes it from siblings like get_securities_lending or get_credit_trading. It is a noun phrase rather than an explicit verb, but the retrieval intent is unambiguous.

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 '[국내 전용]' tag and the note that same-day figures are only finalized in the evening give useful context for when the data is valid, effectively warning against relying on intraday same-day values. However, there is no explicit routing to alternatives (e.g., vs. securities lending or credit trading data) and no stated exclusions beyond the market scope already implied.

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