Skip to main content
Glama
tossinvest-mcp

tossinvest-mcp

by scjang01

섹터 상세 조회

toss_get_sector
Read-only

Retrieves sector details, hierarchy, and period return rates for KR or US markets by sector ID. Use it to inspect sector performance; unavailable periods return null.

Instructions

섹터 상세·계층 및 선택한 시장의 기간별 등락률(소수비율). 미제공 기간은 null. sectorId는 toss_list_sectors에서 확인하세요.

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": {
      "sectorId": "<sectorId>",
      "marketCountry": "<marketCountry>"
    },
    "name": "toss_get_sector"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectorIdYes
marketCountryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/openWorldHint/destructiveHint=false, so safety needs no restating. The description adds value beyond them by disclosing return semantics that have no output schema: change rates are decimal ratios and unavailable periods come back as null. It does not address data freshness or scope limits of openWorld access.

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, front-loaded clauses: what is returned, how values are formatted, and where the key parameter comes from. No filler. The terse noun-phrase style is dense but still parseable.

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?

For a two-parameter read tool with no output schema, the description covers return content, value format, null semantics, and parameter provenance. The remaining ambiguity about the shape of the hierarchy is minor given the tool's simplicity, though marketCountry behavior is only implied.

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 0%, so the description must carry the load. It does tell the agent where sectorId comes from (toss_list_sectors), which is genuinely useful provenance, but it adds nothing about the sectorId pattern/length or about marketCountry beyond the implicit 'selected market', which the enum already encodes.

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 a specific resource and enumerates what is returned: sector detail, hierarchy, and period-based change rates for a chosen market. It is clearly a single-sector lookup rather than a list or ranking, which separates it from siblings like toss_get_sector_rankings or toss_get_sector_etfs. It stops short of explicitly naming those siblings as alternatives.

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?

Useful prerequisite guidance is given: sectorId must be obtained from toss_list_sectors. However, there is no explicit statement of when to use this tool versus the sector sub-resource siblings, and no when-not guidance. Usage is implied rather than spelled out.

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