Skip to main content
Glama
This connector has been deprecated

Replaced by echopai-mcp.

Duplicate listing; superseded by io.github.echopai/echopai-mcp (official MCP Registry entry).

limit_up_analysis

Per-stock limit-up attribution based only on published views and research. Returns leading_concept, concept_tags, nullable reason, attribution_status, empty_reason, evidence_refs and last_attempt_at. Incremental updates depend on service configuration; scheduled generation also maintains processing status. pending, processing, no_verified_catalyst, failed, budget_deferred and legacy_unknown are distinct. Inherited reasons retain their original generation time. Omit trade_date for the latest stored day; pass today explicitly for today's coverage. Optional as_of reads saved versions available at a historical instant without using later evidence.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "limit_up_analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
_jqNoJMESPath,对 data 求值(写 items[*].id)
as_ofNoHistorical cutoff with timezone, no later than now; saved versions only
_spillNotrue=全量落盘,只回摘要与取数地址
_fieldsNo逗号分隔的直接字段;有 items 时投影每行,否则投影 data;外层字段或嵌套结构用 _jq
_intentNo用户原问题一句话,仅分析用,可留空
_max_bytesNo响应字节上限,默认约 50 KB
trade_dateNoISO date YYYY-MM-DD; omit for the latest *attributed* day (falls back to the previous day until today's first slot lands ~09:47 Beijing — pass today explicitly for today's data)
_max_bytes_modeNo正文超限处理,默认 truncate 保留前缀

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantially: it discloses freshness behavior ('incremental updates depend on service configuration'), background maintenance of processing status, the full set of distinct outcome states (pending, processing, no_verified_catalyst, failed, budget_deferred, legacy_unknown), and that inherited reasons keep their original generation time. It omits access/auth or rate-limit characteristics, but the operational semantics that most affect interpretation are covered.

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 content is front-loaded: purpose first, then return fields, then state/freshness semantics, then parameter guidance. Sentences are dense but each contributes. The one status-list sentence ('pending, processing, ... are distinct') is terse to the point of jargon, but it does earn its place.

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?

There is no output schema, so the description correctly enumerates the return fields (leading_concept, concept_tags, nullable reason, attribution_status, empty_reason, evidence_refs, last_attempt_at) and explains the status vocabulary the agent must interpret. Adding the empty_reason/status distinction is what makes the result usable. Minor gap: no statement of what happens for a symbol not in the limit-up universe.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents every parameter including the trade_date fallback and as_of warning. The description largely restates the trade_date and as_of semantics rather than adding new meaning, though the enumeration of attribution_status values (which are outputs, not inputs) helps an agent interpret results. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening clause names a specific verb and resource ('per-stock limit-up attribution') and constrains scope ('based only on published views and research'), which is meaningfully more precise than the bare name. It does not, however, explicitly distinguish itself from likely siblings such as limit_up_pool or limit_up_summary, leaving the agent to infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear calling guidance for the date parameters ('omit trade_date for the latest stored day; pass today explicitly for today's coverage' and as_of for historical versions), which is genuine usage direction. It stops short of when-to-use/when-not guidance against alternative tools — nothing says to use this rather than the pool or views sibling when the question is a plain limit-up list.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources