tossinvest-mcp

Overview Schema Source Related Servers Discussions Admin

get_sector

Read-onlyIdempotent

Retrieve a sector's basic information and its return rates across selectable periods from 1 day to 1 year for Korean or US markets. Use it to compare sector performance by market and timeframe.

Instructions

섹터 기본 정보와 지정 시장 기준 기간별(1d~1y) 등락률을 조회한다.

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": {
      "sector_id": "<sector_id>",
      "market_country": "<market_country>"
    },
    "name": "get_sector"
  }
}

Input Schema

Name	Required	Description	Default
`sector_id`	Yes	섹터 ID. list_sectors 응답의 sectorId
`market_country`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 9, 2026

TDQS

B3.2/5.0

Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds useful context by disclosing what is returned (basic sector info plus per-period change rates from 1d to 1y), but it says nothing about the range of periods supported, missing-data behavior, or how market_country affects results.

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?

One front-loaded sentence with no filler, and the returned content is stated before any modifiers. It is efficient, though it leaves little room for the usage and parameter detail an agent would benefit from.

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 two-parameter read-only tool with annotations and no output schema, the description covers the essentials of what is returned. It is thin on what '기본 정보' comprises and on the semantics of market_country, which the schema does not fill in.

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 50%: sector_id is documented in the schema, while market_country has only an enum (KR/US) and no description. The phrase '지정 시장 기준' implies that market_country selects the market basis for the change rates, which adds some meaning beyond the enum, but the description does not clarify the effect of choosing KR versus US.

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 states a specific verb (조회한다) and a specific resource (섹터 기본 정보 + 기간별 등락률 1d~1y), and it scopes the result by market. An agent can tell it apart from list_sectors or get_sector_stocks, though the description never names those siblings explicitly.

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?

The description contains no when-to-use or when-not-to-use guidance and no prerequisites. The only routing hint, that sector_id comes from a list_sectors response, lives in the input schema rather than the description, so the description itself gives the agent nothing about choosing this tool over its siblings.

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