StockLens

Overview Schema Source Related Servers Discussions Admin

get_indicators_bulk

Read-onlyIdempotent

Bulk-retrieve technical indicator values for up to 100 stocks in parallel to screen and compare aggregate readings without repeated single-stock calls.

Instructions

기술지표벌크 — 여러 종목(최대 100개)의 지표를 병렬 판정. 스크리닝 핵심.

⚠️ 시계열·캔들 아님 — 집계 판정값만(시각화는 get_chart). get_indicators N번 대신 이걸로.

Args: codes: 종목코드 리스트 (최대 100개) days: 조회 일수 (기본 260) include: 지표 키 (기본 ["ma_phase","volume"]). get_indicators 참조. timeframe: "day"/"week"/"month" params: 지표 파라미터 오버라이드(전 종목 공통). get_indicators 참조.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`days`	No
`codes`	Yes
`params`	No
`include`	No
`timeframe`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedv1.1.3Sep 17, 2026
- removedInput schema / properties / days / default
```
Removed value: -260
```
- 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"
```
- 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 / timeframe / default
```
Removed value: -"day"
```
First observedv0.4.0May 29, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds that only aggregated judgment values are returned (not time series) and that params overrides are common to all stocks, which are useful behavioral traits. However, it does not detail output structure or potential performance/rate-limit implications, though the output schema exists to fill some of that gap.

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 well-structured: a concise header with the core purpose, a warning line clarifying what it is not, and a tidy argument list with defaults. It is front-loaded, every sentence earns its place, and the formatting improves scannability.

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?

Given the complexity (5 params, nested objects, output schema present), the description provides enough to call it correctly: parameter defaults, allowed timeframe values, and references to get_indicators for indicator details. It clarifies return type and differentiates from siblings. It does not explain the exact output schema, but the output schema itself covers that, so the description is adequately complete.

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?

Schema description coverage is 0%, so the description must compensate. It lists all 5 parameters with explanations: codes (max 100), days (default 260), include (default values, referencing get_indicators), timeframe (allowed values), and params (override, common to all). This adds meaning beyond the bare types. It could specify include key options more explicitly, but it points to get_indicators for details, which is acceptable.

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's function: it computes indicators for multiple stocks (up to 100) in parallel, specifically for screening. It distinguishes itself from get_indicators (single-stock) and get_chart (visualization) by naming them explicitly, making the purpose 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?

Explicit guidance is given: use this instead of calling get_indicators N times, and use get_chart for visualization. It also clarifies that it returns aggregated judgment values only, not time series/candles, preventing misuse. The mention of '스크리닝 핵심' (core for screening) sets context for when to use it.

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

Deploy Server