StockLens

Overview Schema Source Related Servers Discussions Admin

get_intraday_indicators

Read-onlyIdempotent

Calculate intraday technical indicators from minute/hourly bars for KR/US stocks. Choose interval, number of bars, and indicator keys to analyze MA, MACD, volume, and candlestick patterns.

Instructions

분봉지표 — 분봉/시간봉 기준 기술지표 (JSON).

차트와 같은 봉 데이터로 계산한다(공급원 혼합 없음). 일봉 지표는 기존 get_indicators 사용. days 가 아니라 bars(봉 개수) 기준이다.

분봉은 일봉과 키 이름이 다르다 — 이름 그대로 읽으세요: position.lookback_high/low 조회한 봉 구간의 고가·저가. 52주 값이 아님 ma_cross·macd.cross 의 bars_ago 몇 봉 전인지 volume.trade_value_est_krw / _usd 종가×거래량 추산. 통화는 이름대로 미국 가격은 달러 소수 둘째 자리(1달러 미만은 넷째 자리)

Args: symbol: KR 종목코드 또는 US 티커 market: "KR" | "US" interval: 1m|3m|5m|10m|15m|30m|60m|120m|240m bars: 계산에 쓸 봉 개수 (기본 260, 30~500) include: 지표 키 (기본 ["ma","ma_phase","volume","candle"]) venue / session / completed_only / source: get_intraday_chart 와 동일 params: 지표 파라미터 오버라이드

Input Schema

TableJSON Schema

Name	Required	Description	Default
`bars`	No
`venue`	No
`market`	No
`params`	No
`source`	No
`symbol`	Yes
`include`	No
`session`	No
`interval`	No
`completed_only`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed17 schema fields changedv1.1.3Sep 17, 2026
- removedInput schema / properties / bars / default
```
Removed value: -260
```
- removedInput schema / properties / completed_only / default
```
Removed value: -true
```
- removedInput schema / properties / include / anyOf
```
Removed value: -[
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / include / default
```
Removed value: -null
```
- addedInput schema / properties / include / items
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / include / type
```
Added value: +"array"
```
- removedInput schema / properties / interval / default
```
Removed value: -"60m"
```
- removedInput schema / properties / market / default
```
Removed value: -"KR"
```
- addedInput schema / properties / params / additionalProperties
```
Added value: +true
```
- removedInput schema / properties / params / anyOf
```
Removed value: -[
-  {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / params / default
```
Removed value: -null
```
- addedInput schema / properties / params / type
```
Added value: +"object"
```
- removedInput schema / properties / session / default
```
Removed value: -"regular"
```
- removedInput schema / properties / source / default
```
Removed value: -"auto"
```
- removedInput schema / properties / venue / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / venue / default
```
Removed value: -null
```
- addedInput schema / properties / venue / type
```
Added value: +"string"
```
Addedv1.0.1Sep 13, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent safety, and the description adds valuable behavioral context: same bar data as the chart with no source mixing, distinct key names, lookback_high/low not being 52-week values, bars_ago counted in bars, and estimated trade values. This goes beyond the annotations without contradicting them.

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?

The description is front-loaded with the definition and the most critical caveats (bars vs days, key-name differences), followed by a compact Args list. Every sentence adds needed information, and the bulleted key-name warnings are dense and directly prevent misinterpretation.

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 10-parameter nested-object tool with an output schema, the description is nearly complete: it covers all parameters, gives defaults and enums, and clarifies important output-name semantics without restating the schema. It falls slightly short of 5 because four parameters depend on get_intraday_chart documentation and the params override is underspecified.

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

Parameters4/5

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

With 0% schema coverage, the description carries the full parameter burden and mostly succeeds: it gives market and interval enums, bars default and range, include default list, and delegates venue/session/completed_only/source to get_intraday_chart semantics. The only weak spot is 'params: 지표 파라미터 오버라이드', which lacks format or key details.

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 a precise label, '분봉지표 — 분봉/시간봉 기준 기술지표 (JSON)', naming the resource and scope. It explicitly says daily indicators belong to get_indicators, so the tool is clearly distinguished from its closest sibling.

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 explicitly states when to use this tool (intraday/minute/hour bars) and when not to ('일봉 지표는 기존 get_indicators 사용'). It also clarifies the bars-not-days unit and references get_intraday_chart for shared parameter semantics, giving the agent clear routing guidance.

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

Deploy Server