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_lockups

Scan upcoming share-lockup expirations across the whole A-share market for the next N days, sorted by unlock date then unlock pct desc. Forward-looking sell-pressure radar that digest can't provide (digest is single-code). Filter small unlocks with min_pct (percentage points of total shares); pass codes to restrict to a portfolio instead of the whole market.

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

Input Schema

NameRequiredDescriptionDefault
_jqNoJMESPath,对 data 求值(写 items[*].id)
daysNoForward window in days (1-90, default 30)
codesNoComma-separated canonical codes (max 200) to filter a portfolio; omit to scan the whole market
limitNoMax rows (1-1000, default 200)
_spillNotrue=全量落盘,只回摘要与取数地址
_fieldsNo逗号分隔的直接字段;有 items 时投影每行,否则投影 data;外层字段或嵌套结构用 _jq
_intentNo用户原问题一句话,仅分析用,可留空
min_pctNoMinimum unlock pct of total shares (percentage points, default 0)
_max_bytesNo响应字节上限,默认约 50 KB
_max_bytes_modeNo正文超限处理,默认 truncate 保留前缀

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/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; it discloses the market-wide default scope, the forward-looking window, and the result ordering, which are real behavioral traits. It stops short of stating that this is a pure read with no side effects or describing volume/pagination behavior at the row level, so it is strong but not complete for an unannotated tool.

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?

Three sentences, front-loaded with the core action and scope before differentiation and filter hints, with no filler. The parenthetical about digest costs a few words but earns them by preventing a wrong tool choice.

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 scan tool with ten parameters (seven of them generic plumbing) and no output schema, the description covers the parameters that actually change results and explains the returned ordering. It would be fully complete if it noted briefly what each row contains or how `limit` interacts with the market-wide default, but nothing essential is missing to invoke 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 defines days, codes, min_pct, limit, and the plumbing parameters. The description reinforces the intent of `min_pct` ('filter small unlocks') and `codes` ('restrict to a portfolio'), adding framing but no syntax or units beyond what the schema states. 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 ('Scan upcoming share-lockup expirations'), the scope ('whole A-share market'), the time window ('next N days'), and even the sort order ('unlock date then unlock pct desc'). It also names the sibling it differs from ('digest') and why, so an agent can separate the two without opening either schema.

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?

Gives explicit routing guidance: use this for forward-looking sell-pressure because 'digest is single-code', use `min_pct` to suppress noise from small unlocks, and pass `codes` when a portfolio is the target rather than the whole market. Both the when-to-use and the how-to-narrow conditions are spelled out.

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