Skip to main content
Glama
Sign In
tossinvest-mcp

tossinvest-mcp

by clauzewitz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_sector_etfs

Read-onlyIdempotent

Retrieve ETF symbols and names for a given sector in Korean or US markets. Use the sector ID from sector listings to identify matching ETFs; fetch quotes separately.

Instructions

섹터 관련 ETF 의 심볼·이름을 조회한다 (하위 섹터 미포함).

시세는 get_prices 로 조회한다.

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

Input Schema

NameRequiredDescriptionDefault
sector_idYes섹터 ID. list_sectors 응답의 sectorId
market_countryYesKR 국내 상장 ETF, US 미국 상장 ETF

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent and open-world behavior, so the bar is lower. The description still adds genuine behavioral value by disclosing the result contents (symbols and names, no prices) and the scope limit that sub-sector ETFs are excluded — a constraint an agent would otherwise get wrong.

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, both load-bearing: the first states the resource and scope, the second routes to the pricing tool. Front-loaded and free of padding.

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-required-parameter read-only lookup with no output schema, the description covers what is returned (symbols and names), what is excluded, and where to go for quotes; the sector_id provenance is covered by the schema. Only minor gaps remain, such as whether an empty list is possible for a sector with no ETFs.

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%: sector_id is tied to list_sectors' sectorId and market_country has a KR/US enum with meanings, so the schema carries the parameter burden. The description adds no further parameter semantics beyond what the schema already says.

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: retrieves the symbols and names of sector-related ETFs, and explicitly narrows scope with '(하위 섹터 미포함)'. It is distinguishable from get_prices via the explicit routing sentence, though it does not explicitly differentiate itself from nearby siblings like get_sector or get_sector_stocks.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear routing: use get_prices for quotes, implying this tool only resolves ETF identity, and excludes sub-sector ETFs from the result. It lacks an explicit 'when not to use' versus get_sector_stocks/get_sector_rankings, but the context is unambiguous enough for an agent.

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