Skip to main content
Glama
tossinvest-mcp

tossinvest-mcp

by clauzewitz

get_sector_rankings

Read-onlyIdempotent

Retrieve sector rankings for Korean and US markets, sorted by gainers or trading amount over selected periods, to compare sector performance and market activity.

Instructions

섹터 랭킹(대·중분류, 최대 100위)을 조회한다.

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": {
      "type": "<type>",
      "market_country": "<market_country>"
    },
    "name": "get_sector_rankings"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesTOP_GAINERS 등락률 상위, MARKET_TRADING_AMOUNT 거래대금 상위
durationNo1d
market_countryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/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. The description usefully adds that results are capped at rank 100 and cover large/medium sector tiers, but says nothing about how duration changes the ranking basis or what happens when a market has fewer than 100 sectors.

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?

A single compact sentence with no wasted words, and the scope qualifier is front-loaded. It is efficiently written, though it is arguably too terse for a tool with an undocumented lookback parameter.

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?

With three parameters, no output schema, and annotations already covering the read-only profile, the description is minimally adequate. However, for a ranking tool with no output schema, it should at least indicate what a ranking entry contains (sector identifier, rank, metric value) and how duration affects results.

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 coverage is only 33% — the 'duration' parameter has no description at all, and the description does not compensate by explaining that duration sets the lookback window for the ranking. The description does add sector-tier semantics ('대·중분류') and the rank cutoff, which are not in the schema, so it contributes some value beyond the enum definitions.

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?

States a specific verb+resource ('섹터 랭킹 ... 조회한다') and adds scope detail: large/medium sector classification and a top-100 cap. It does not name or contrast against close siblings such as get_stock_rankings or get_investor_trading_rankings, so the agent must infer the distinction from the resource name alone.

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 guidance on when to pick this over get_stock_rankings, get_investor_trading_rankings, or list_sectors, and no mention of prerequisites or market-coverage constraints. The agent is left to infer usage entirely from the resource noun.

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