Skip to main content
Glama

Ashares Unlock Calendar

ashares_unlock_calendar
Read-onlyIdempotent

China A-share restricted-share unlock calendar (限售股解禁): which stocks have locked-up shares becoming tradable on a given day or date range, ranked by unlock market value or by share of float. Answers "today's unlock list", "解禁日历", "限售股解禁 2026-11-06 top 10 by market value", "how many stocks unlock next week", "when does 603376 unlock", "解禁市值排名". Each unlock has the stock, unlock date, restricted-share type (e.g. first-day original-holder shares, IPO strategic placement, private-placement shares), shares unlocking, market value at the latest price in CNY, percent of total shares and percent of the pre-unlock tradable float, number of holder batches, and the stock's price change over the 20 trading days before and after. Also returns the per-day total: number of unlocking stocks and their combined market value. Give date, or from and to (max 31 days), or neither for today; symbol (6-digit code) lists that stock's unlock dates. Source: Eastmoney datacenter, restricted-share unlock report (keyless).

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "date": "2026-11-06",
      "limit": 10
    },
    "name": "ashares_unlock_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoRange end (YYYY-MM-DD).
dateNoSingle unlock day, YYYY-MM-DD or YYYYMMDD (default: today).
fromNoRange start (YYYY-MM-DD); use with `to`. Max span 31 days.
sortNoRank by unlock market value (default) or by percent of pre-unlock tradable float.
limitNoMax unlock rows returned, 1-100 (default 20). Per-day totals always cover every unlock fetched.
symbolNo6-digit A-share code (e.g. "603376"): list only that stock's unlocks (default window: 1 year back to 1 year ahead if no date given).

Output Schema

NameRequiredDescriptionDefault
toNo
fromNo
foundNo
sourceNo
symbolNo
messageNo
per_dayNo
unlocksNo
returnedNo
sorted_byNo
data_as_ofNo
field_notesNo
rows_fetchedNo
total_unlock_rowsNo
per_day_totals_completeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds real context beyond them: the keyless Eastmoney datacenter source, the 31-day span cap, and the fact that per-day totals cover every unlock fetched even when `limit` truncates rows. It does not discuss rate limits, freshness/lag of the latest price used for market value, or error behavior.

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 with the resource and definition, then field inventory, then parameter rules, then source. Dense but every block is functional; the quoted natural-language query phrases are somewhat repetitive yet serve intent matching. No filler or marketing language.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, annotations covering safety and idempotency, and full parameter documentation, this description supplies exactly the remaining context: what an unlock record contains, the per-day aggregate, the date/symbol modes, span limits, ranking dimension, and provenance. Nothing an agent needs in order to select and call it correctly is missing.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3; the description earns above that by adding semantics the schema lacks, notably the default window for `symbol` (1 year back to 1 year ahead when no date is supplied) and that ranking is by unlock market value or percent of pre-unlock tradable float. It does lightly restate schema-covered constraints (max 31 days, 6-digit code).

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 resource and domain up front: 'China A-share restricted-share unlock calendar (限售股解禁)', with an explicit definition of what it returns (which stocks unlock on a day or range, ranked by market value or float ratio). The query examples ('today's unlock list', '解禁市值排名', 'when does 603376 unlock') remove any ambiguity versus generic calendar or quote tools.

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?

Gives concrete invocation patterns: pass `date`, or `from`+`to` (max 31 days), or neither for today, and `symbol` to pivot to a single stock's schedule. What is missing is explicit routing guidance against a potentially adjacent sibling such as release_calendar_markets (other markets); the agent must infer that this tool is the A-share-specific one.

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.