Skip to main content
Glama
Johnhyeon

StockLens

by Johnhyeon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_us_multi_diagnosis

Read-onlyIdempotent

Batch-analyze up to 20 US tickers at once, returning completed-bar chart stats (returns, 52-week position, volume) and technical indicators (MA, cross, RSI) for multi-stock diagnosis.

Instructions

US multi diagnosis — 미국 다종목 차트 통계·완성 봉 기술 상태 배치 (JSON).

"고정 15종목 단계 진단", "관심종목 기술 상태 일괄 점검" 같은 반복 판정에 사용합니다. 종목당 get_us_chart + 지표 계산을 반복 호출하는 대신 한 번에: 차트 통계(완성 봉 종가·5/20/60일 수익률·52주 위치·평균 거래량)와 기술 상태(MA20/60·20-60 크로스·RSI14)를 완성 봉 기준으로 돌려줍니다.

이 도구는 종목을 단일 점수로 압축하지 않습니다. 판정 재료(원값)를 그대로 보존하고, 확인 불가는 unavailable 로 남깁니다 - 등급·점수·순위를 만들어 붙이는 것은 읽는 쪽의 몫이고, 그때도 근거 수치가 함께 있어야 합니다.

Args: tickers: US 티커 리스트 (최대 20개) include: 선택 결합 섹션. "estimates"(애널리스트 EPS 추정 변화), "earnings"(최근 실적 서프라이즈), "short"(공매도 지표+보고 최신성). 기본 None = 차트·기술 상태만.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
includeNo
tickersYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.1.3
    • 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"
  2. Addedv1.0.1

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare read-only/idempotent/non-destructive, and the description adds real behavioral context: results are based on completed bars only, unavailable confirmations are preserved as 'unavailable', and the tool does not compress tickers to a score/rank. These constraints materially affect how an agent should interpret and present results.

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 the core purpose and output contents, then the no-scoring caveat, then parameter semantics. The prose is dense and every sentence adds useful information, though the philosophy paragraph could be slightly tighter without losing value.

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?

For a 2-parameter batch tool with a rich output schema and read-only/idempotent annotations, the description covers invocation constraints, optional section semantics, default behavior, and data-quality handling. There is no material information an agent needs that is omitted.

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 coverage and no enums, the description carries the full burden and succeeds: tickers are defined as a US ticker list capped at 20, and include is defined as optional sections with the exact accepted strings ('estimates', 'earnings', 'short'), their meaning, and the default None behavior.

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 ('returns') and resource: a one-call batch of chart statistics (close, 5/20/60-day returns, 52-week position, average volume) and technical status (MA20/60, cross, RSI14) for multiple US tickers. It also explicitly contrasts itself with repeated per-ticker get_us_chart calls, so an agent can distinguish it from the chart siblings.

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?

Gives clear use context: repeated fixed-15 ticker diagnostics or watchlist technical-status checks. It names the alternative (looping get_us_chart plus indicator computation) and says this tool replaces it, but it does not explicitly list when-not scenarios or compare with other multi-stock siblings like get_multi_chart_stats.

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