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

digest

One-shot research digest for one security: views (PRIMARY), quote, valuation snapshot, market sentiment, supplementary news, ownership_events (30-day insider trades + buybacks, next-30-day lockups) and margin (~7 trading days). Margin is T+1 — judge direction by financing_net_buy_cny, never gross financing_buy_cny. Separate buckets, not ranked against each other; partial failures go to meta.partial_failures[]. First call for 'what's going on with '. A-share returns all buckets; HK/US return only views + news. A+H: pass the A-share canonical.

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": {
      "code": "<code>"
    },
    "name": "digest"
  }
}

Input Schema

NameRequiredDescriptionDefault
_jqNoJMESPath,对 data 求值(写 items[*].id)
codeYesCanonical code: A-share SSE:600519 | HK HK:00700 | US US:BABA. HK/US return only views+news. Use `lookup` first if you only have a name.
_spillNotrue=全量落盘,只回摘要与取数地址
_fieldsNo逗号分隔的直接字段;有 items 时投影每行,否则投影 data;外层字段或嵌套结构用 _jq
_intentNo用户原问题一句话,仅分析用,可留空
_max_bytesNo响应字节上限,默认约 50 KB
news_hoursNoLookback for news bucket (hours, default 24 — event horizon)
_max_bytes_modeNo正文超限处理,默认 truncate 保留前缀
limit_per_bucketNoPer-bucket item cap (views/news). Quote/snapshot/sentiment aren't paginated here.
views_since_daysNoLookback for views bucket (days, 1-30; views feed caps at 30d). For longer research history use the `views` verb's from/to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/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 so well: it discloses partial-failure handling (meta.partial_failures[]), the T+1 margin caveat and which field to judge direction by, that buckets are separate and not ranked, and the per-market bucket coverage. These are non-obvious behavioral traits an agent could not infer from the schema.

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?

Dense and front-loaded, leading with the purpose and the primary bucket before caveats. The telegraphic style packs a lot in, though the run-on bucket list and mid-sentence caveats slightly reduce 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?

For a complex composite tool with ten parameters and no output schema, the description covers bucket composition, failure semantics, and market-specific coverage. It stops short of describing the overall response envelope, but the partial_failures pointer and bucket list give an agent enough to call it correctly.

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 all ten parameters including defaults and ranges. The description adds only marginal meaning beyond it (the A+H canonical-code rule), so the baseline 3 applies.

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 and resource ('one-shot research digest for one security') and enumerates the buckets it returns (views, quote, valuation snapshot, sentiment, news, ownership_events, margin). This clearly distinguishes it from single-purpose siblings like news, quote, and views.

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?

Explicitly routes the agent with 'First call for "what's going on with <stock>"' and clarifies coverage differences (A-share returns all buckets; HK/US only views+news; A+H pass the A-share canonical). It does not name a when-not-to-use case or point to a specific alternative for deeper dives, keeping it just short of a 5.

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