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

ownership_show

Ownership events for one A-share: recent insider holder trades (net shares/pct, increase/decrease counts), share repurchases (ongoing count, executed amount/shares, latest status) and upcoming lockup expirations (unlocking shares/pct, next date). Holder-trade / repurchase windows look back N days; lockups look forward. ⚠️ A repurchase price ceiling BELOW the current quote is almost certainly a restricted-share cancellation at grant price, not open-market support. ⚠️ plan_expires_on is usually null = UNKNOWN, not still valid — use disclosed_days_ago. T+1.

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": "ownership_show"
  }
}

Input Schema

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

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 real work: it warns that a repurchase price ceiling below the current quote is likely a restricted-share cancellation rather than open-market support, and that `plan_expires_on` null means UNKNOWN rather than still valid. It also discloses T+1 data latency. It does not address auth, rate limits, or error conditions, but for a read-only market-data tool the caveats provided are the ones most likely to cause misinterpretation.

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 and dense: the payload is described first, then the window semantics, then the two ⚠️ caveats and the T+1 note. Every sentence earns its place, though the telegraphic style (sentence fragments, trailing 'T+1.') costs a little readability.

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 10-parameter tool with no annotations and no output schema, the description does the necessary compensating work by sketching the returned metrics per section and flagging the two most misleading fields. What is missing is any statement of the response envelope or how the three sections are keyed, which the absent output schema would otherwise have covered.

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 all ten parameters, including the three window parameters and the `_jq`/`_spill`/`_fields` machinery, are already documented in the schema. The description's restatement of lookback-versus-forward windows largely duplicates the schema wording, so it adds little beyond the baseline.

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 first sentence names the resource and enumerates the three data families returned (insider holder trades, share repurchases, lockup expirations) with sub-fields, so an agent knows exactly what it gets. It does not, however, distinguish itself from the sibling `ownership_lockups`, which is a real ambiguity given this tool also returns lockup expirations.

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?

Usage is implied by the data families and by the sentence 'Holder-trade / repurchase windows look back N days; lockups look forward,' which tells the agent how to reason about the windows. There is no explicit when-to-use guidance, no mention of when to prefer `ownership_lockups` for pure lockup queries, and no stated preconditions.

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