Skip to main content
Glama
Johnhyeon

StockLens

by Johnhyeon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

get_theme_stocks

Read-onlyIdempotent

Fetch theme-specific stock lists for sectors like AI, semiconductors, or batteries. Supports partial theme matching, pagination, and change-rate sorting to identify both top gainers and undervalued stocks.

Instructions

테마종목 — 특정 테마에 속한 종목 리스트를 가져옵니다. "반도체 테마 종목", "2차전지 관련주", "AI 테마주" 같은 질문에 사용합니다. 테마명 부분 매칭을 지원합니다.

⚠️ 등락률 내림차순으로 반환합니다. count로 자르면 그날 많이 오른 종목만 남고 소외된(많이 내린) 종목은 뒤쪽 쪽으로 밀립니다. 결과 머리말에 테마 전체 종목 수와 이 쪽의 범위("전체 N개 중 1~30번째")가 나옵니다. 저평가·소외 종목을 찾는 용도라면 count를 전체 종목 수로 주거나(최대 500) 꼬리말의 page=로 이어 받으세요. 시가총액 기준 모집단이 필요하면 get_market_cap_ranking을 쓰세요.

Args: theme_name: 테마명 (예: "2차전지", "AI", "반도체") count: 한 번에 받을 종목 수 (기본 30, 최대 500) include_reason: 편입사유 포함 여부. False로 하면 토큰 대폭 절감. "왜 이 테마에 들어갔는지" 필요 없으면 False 권장. page: count 개씩 나눈 몇 번째 쪽인가 (기본 1). page=2, count=30 이면 31~60번째.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
countNo
theme_nameYes
include_reasonNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses important behavior: results are sorted by change rate descending, truncating with count pushes laggards to the end, the header contains total and range, and the tail provides page= continuation. It also warns about the page ordering consequence for undervalued-stock use cases.

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?

Front-loaded with purpose, then behavior, then a clearly labeled Args section. It is slightly verbose and contains a typo ('뒤쪽 쪽으로'), but each section earns its place for the complexity being described.

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 all the semantics an agent needs to call this tool: scope, ordering trap, pagination, max count, token-saving option, and an alternative for market-cap ranking. The presence of an output schema means return-value structure does not need to be restated, and the existing annotations cover safety.

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?

Although schema description coverage is 0%, the description documents all four parameters: theme_name with examples, count with default and max (30/500), include_reason with token-saving benefit and recommendation, and page with a concrete paging example (page=2, count=30 => 31~60).

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 opening line names a specific verb and resource: '특정 테마에 속한 종목 리스트를 가져옵니다' (fetch list of stocks belonging to a theme). It gives concrete query examples and notes partial theme-name matching, so an agent can distinguish it from tools like list_themes or ranking tools.

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?

The description states when to invoke it (e.g., '반도체 테마 종목', '2차전지 관련주', 'AI 테마주') and routes to an explicit alternative when a market-cap-based population is needed: '시가총액 기준 모집단이 필요하면 get_market_cap_ranking을 쓰세요'. It also gives scenario-specific advice for finding undervalued stocks via count/page settings.

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