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).

technicals

KEY FIELDS (per item): pos_in_52w.value (0–1, plus high_52w / low_52w / breakout_52w / breakdown_52w), consecutive_up.days + .pct_change, volume_spike.median_next_ret_pct / .avg_next_ret_pct / .winrate / .sample_size (no next_day_median_pct), overhead.supply_days / .traded_amount_ratio. Every block has observed_days + status (no_data = insufficient history). End-of-day technicals for up to 50 A-shares on one server-side methodology. Use scan / limit_up_pool to find candidates, this to vet them. Read winrate only with sample_size, the Wilson interval and excess_winrate — samples are often single-digit.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "codes": "<codes>"
    },
    "name": "technicals"
  }
}

Input Schema

NameRequiredDescriptionDefault
_jqNoJMESPath,对 data 求值(写 items[*].id)
codesYesCanonical codes, 1-50 (e.g. SZSE:300759)
_spillNotrue=全量落盘,只回摘要与取数地址
_fieldsNo逗号分隔的直接字段;有 items 时投影每行,否则投影 data;外层字段或嵌套结构用 _jq
_intentNo用户原问题一句话,仅分析用,可留空
_max_bytesNo响应字节上限,默认约 50 KB
_max_bytes_modeNo正文超限处理,默认 truncate 保留前缀

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose real behavior: server-side methodology (results are not locally recomputable), EOD cadence, a 50-code cap, per-block observed_days + status with no_data meaning insufficient history, and the explicit absence of next_day_median_pct. It omits operational traits such as rate limits, latency, or what happens when some codes in a batch have no data, which keeps it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is dense but the ordering is inverted: a parenthetical field inventory leads, and the actual purpose statement ('End-of-day technicals for up to 50 A-shares...') arrives third. The 'KEY FIELDS' block earns its place given there is no output schema, but the run-on parenthetical mixing field names with sample-size warnings is harder to parse than separate labeled lines would be.

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?

With no output schema and no annotations, the description correctly shoulders the return-shape burden by naming the fields an agent will consume and flagging that winrates on single-digit samples are unreliable. The remaining gap is the shared plumbing parameters (_spill, _jq, _fields, _max_bytes), which are neither explained here nor described in English in the schema, so an agent cannot learn how to page or project results from this definition alone.

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 coverage is 100%, so the baseline of 3 applies and the schema already documents all seven parameters. The description never mentions codes, _jq, _spill, _fields, _intent, _max_bytes, or _max_bytes_mode, so it adds no meaning about the 1-50 code constraint or the projection/truncation controls beyond what structured data provides. Its field discussion describes outputs, not inputs.

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?

States a specific resource and scope: 'End-of-day technicals for up to 50 A-shares on one server-side methodology', and distinguishes itself from 'scan / limit_up_pool' as the vetting step. The verb+resource is unambiguous, but the purpose sentence is placed third, after a field inventory, so an agent skimming the first line sees key names rather than what the tool does.

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?

Explicitly names the alternative tools and the selection rule: use scan/limit_up_pool to find candidates, this tool to vet them. It adds a second conditional instruction ('Read winrate only with sample_size, the Wilson interval and excess_winrate') that tells the agent when a returned field is not trustworthy. This is exactly the when-to-use / when-to-distrust guidance the dimension asks for.

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