Skip to main content
Glama
Johnhyeon

StockLens

by Johnhyeon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

get_sector_stocks

Read-onlyIdempotent

Retrieve stocks by sector name from Korean market, sorted by daily change rate. Supports partial sector names and pagination for large sectors.

Instructions

업종종목 — 특정 업종에 속한 종목 리스트를 가져옵니다. "통신장비 업종 종목", "반도체 업종", "제약 섹터 종목" 같은 질문에 사용합니다. 업종명 부분 매칭을 지원합니다.

⚠️ 등락률 내림차순으로 반환합니다. count로 자르면 그날 많이 오른 종목만 남고 소외된(많이 내린) 종목은 뒤쪽 쪽으로 밀립니다. 결과 머리말에 업종 전체 종목 수와 이 쪽의 범위("전체 175개 중 1~30번째")가 나옵니다. 업종 전체를 보려면:

  • 500종목 이하 업종: count를 머리말의 전체 수로 주세요 (예: 제약 175 → count=175).

  • 그보다 큰 업종(예: '기타' 약 1,500종목): count=500 으로 page=1, 2, 3, 4 를 차례로. 꼬리말에 다음 쪽 호출법이 나옵니다. 쪽은 같은 순간의 목록에서 자릅니다(장중 5분 캐시). 몇 분 넘게 띄워 받으면 그 사이 등락률 순서가 바뀌어 경계 종목이 겹치거나 빠질 수 있습니다.

Args: sector_name: 업종명 (예: "통신장비", "반도체", "제약") count: 한 번에 받을 종목 수 (기본 30, 최대 500) page: count 개씩 나눈 몇 번째 쪽인가 (기본 1). page=2, count=30 이면 31~60번째.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
countNo
sector_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.3
    • removedInput schema / properties / count / default
      Removed value: -30
    • addedInput schema / properties / page
      Added value: +{
+  "title": "Page",
+  "type": "integer"
+}
  2. First observedv0.4.0

TDQS

A4.8/5.0
Behavior5/5

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

Adds substantial behavior beyond the readOnly/idempotent annotations: results are returned in descending order by 등락률, the header and footer expose pagination context, and the 5-minute cache plus ordering drift can cause overlapping or missing boundary stocks. This is exactly the kind of operational nuance an agent needs.

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?

Long but tightly structured: core purpose and examples come first, followed by important caveats and then parameter details. Every sentence carries operational value, and the warnings about pagination and cache are essential rather than filler.

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?

The description covers matching, ordering, pagination, caching, and full-sector retrieval strategy. Since the output schema and annotations already cover return shape and safety, nothing critical is missing 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?

With 0% schema description coverage, the description fully compensates: sector_name is explained with examples, count gets default and maximum values, and page is illustrated with page=2, count=30 yielding positions 31-60. No parameter is left ambiguous.

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?

States a specific verb and resource: 특정 업종에 속한 종목 리스트를 가져옵니다, and gives concrete example queries like 통신장비 업종 종목 and 제약 섹터 종목. The sector-scoped semantics clearly distinguish it from sibling tools like get_theme_stocks or list_sectors.

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?

Explicitly says when to use it, including sector-name partial matching and example user questions. It also gives detailed pagination strategies for full-sector retrieval, but it does not explicitly name alternative tools to use for non-sector lists, so exclusions are implied rather than stated.

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