Skip to main content
Glama
Johnhyeon

StockLens

by Johnhyeon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

get_etf_list

Read-onlyIdempotent

Search and filter the complete ETF list by category, name keyword, market cap, volume, NAV, or 3-month return to locate matching funds.

Instructions

ETF목록 — ETF 전체 목록 조회, 카테고리·이름 키워드 필터링.

category: 카테고리 필터 (빈 문자열=전체). 가능한 값: "국내 시장지수", "국내 업종/테마", "국내 파생", "해외 주식", "원자재", "채권/금리", "단기자금" keyword: ETF 이름에 포함된 키워드로 필터 (예: "우주", "반도체", "배당"). "OO 테마 ETF 뭐 있어" 같은 질문은 category를 추측하지 말고 keyword로 바로 찾는다 — 한국 ETF는 이름 자체가 테마를 직설적으로 담는 관행이라 (예: "TIGER 미국우주테크") 이름 검색만으로 대부분 커버된다. 단, 특정 회사(예: 비상장사)를 "보유"한 ETF를 찾는 건 이 키워드로 안 된다 — 그 회사명이 ETF 이름 자체에 없으면 못 찾으니, 후보 ETF를 좁힌 뒤 get_etf_info로 구성종목을 직접 확인해야 한다. sort_by: 정렬 기준, 전부 큰 값이 앞 — "marketSum"(시가총액, 기본), "quant"(거래량), "threeMonthEarnRate"(3개월 수익률 높은 순 — 손실이 큰 ETF는 맨 뒤), "nav"(주당 NAV). 1·6·12개월 수익률과 배당은 목록에 없어 정렬할 수 없다(종목별 get_etf_info 로 확인). limit: 반환 개수 (기본 20, 최대 50)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
keywordNo
sort_byNo
categoryNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.1.3
    • removedInput schema / properties / category / default
      Removed value: -""
    • removedInput schema / properties / keyword / default
      Removed value: -""
    • removedInput schema / properties / limit / default
      Removed value: -20
    • removedInput schema / properties / sort_by / default
      Removed value: -"marketSum"
  2. Changed1 schema field changedv0.6.5
    • addedInput schema / properties / keyword
      Added value: +{
+  "default": "",
+  "title": "Keyword",
+  "type": "string"
+}
  3. First observedv0.4.0

TDQS

A5/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld/idempotent, and the description adds valuable behavioral details: sort direction (larger values first), the exclusion of 1/6/12-month returns and dividends from sortable fields, and the need to use get_etf_info for those. No contradiction with annotations.

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?

Despite the length, every sentence adds necessary information. The opening line states purpose, and parameter clarifications are tightly scoped with concrete examples. No filler or redundant restatement of the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description does not need to document return fields. It covers all inputs, sorting behavior, limitations, and directs the user to the correct sibling tool for missing data. The definition is fully sufficient for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full parameter burden. It explains every parameter: category values, keyword semantics and examples, sort_by options with behavior, and limit defaults/maximum. This fully compensates for the schema gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with 'ETF 전체 목록 조회' (retrieve full ETF list), naming a specific verb and resource, and immediately states the two filtering dimensions. This clearly distinguishes it from the sibling get_etf_info, which is per-ETF detail.

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

Usage Guidelines5/5

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

Explicit guidance is given for when to use keyword vs category, including the instruction not to guess category for theme queries and the limitation that holding-company names not in the ETF name require get_etf_info. This is direct when-to-use and when-not-to-use advice relative to a sibling tool.

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