Skip to main content
Glama
Johnhyeon

StockLens

by Johnhyeon

get_indicators

Get technical indicators like moving averages, RSI, MACD, and Bollinger Bands to screen or filter stocks by numeric thresholds. Returns quantitative verdicts, not OHLCV data.

Instructions

기술지표 — 이평선·RSI·MACD·볼린저·스토캐스틱 등 종합 판정 (JSON).

스크리닝·조건 필터·상태 판정 등 숫자 비교가 필요할 때만 호출. 차트 시각화용 아님(시각화는 get_chart). OHLCV 대신 판정 결과만 반환해 토큰 절약. 반환값의 라벨 필드(phase_label, type_label, position 등)는 그대로 인용할 것.

키 이름이 곧 정의입니다 — 임의로 바꿔 읽지 마세요: volume.latest(+latest_date) 마지막 의 거래량. '오늘'이 아님 volume.avg_20b / ratio_vs_avg_20b 20(거래일) 평균 대비 volume.trade_value_est_krw 종가×거래량 추산. 실제 거래대금과 다름 volume.volume_rank_252b 252봉 중 순위, 1이 최다 position.bars_since_high/low 달력일이 아니라 봉 개수. 달력일이 필요하면 high_date/low_date로 직접 계산하세요. _meta.data_basisin_progress_bar면 마지막 봉이 미마감이라 이 판정들은 장 마감 시 달라질 수 있습니다.

Args: code: 종목코드 (예: "005930") days: 조회 일수 (기본 260, 30~500). 구조 분석 지표는 500+ 권장. include: 지표 키. 기본 ["ma", "ma_phase", "volume", "candle"]. 스냅샷: ma ma_phase ma_slope ma_cross rsi macd bollinger stochastic obv volume position candle 구조: support_resistance volume_profile price_channel timeframe: "day"/"week"/"month" (분봉 미지원) params: 비표준 파라미터 오버라이드(사용자 명시 요청 시만). 예: {"rsi":{"period":21}}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYes
daysNo
paramsNo
includeNo
timeframeNoday

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations are provided, but the description extensively explains output semantics, including caveats like trade_value_est being an estimate and data_basis possibly being in_progress_bar. It does not explicitly state the tool is read-only, but the query-oriented nature and lack of side effects are implied. The detailed field explanations compensate for missing explicit annotations.

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?

The description is lengthy due to detailed field semantics, but it is well-structured with sections and bullet points. Each piece of information is relevant and aids comprehension, though some repetition of Korean terms (e.g., '봉') could be streamlined. Overall, it is informative without excess 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 the tool's purpose, usage conditions, parameter details, output field meanings, and data timing caveats. It also distinguishes from chart visualization and notes the tool's suitability for numeric comparisons. This provides a comprehensive understanding necessary for correct usage without external references.

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?

The description includes an 'Args' section that explains each parameter: code, days, params, include, timeframe, with defaults and allowed values. For example, it specifies that 'include' accepts a list of indicator keys and provides the default, and 'params' allows overriding indicator-specific settings like RSI period. This fully clarifies parameter usage.

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 clearly states the tool provides technical indicators (이평선, RSI, MACD, 볼린저, 스토캐스틱) and judgments. It also explicitly distinguishes its purpose from chart visualization, specifying it should be used for numeric comparisons, making the tool's intent unambiguous.

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 gives explicit usage guidance: call only for screening, condition filtering, or status judgment requiring numeric comparison, and not for visualization (pointing to get_chart). It also provides field-level interpretation notes, such as 'latest_date' meaning the last bar, not today, which helps users apply the tool correctly.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Johnhyeon/stocklens-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server