Skip to main content
Glama

Ashares Etf Shares

ashares_etf_shares
Read-onlyIdempotent

Disclosed fund-share-count (基金份额) and net-asset history for a Chinese-listed ETF, period-end total shares outstanding (期末总份额), the period's subscriptions/redemptions (期间申购/赎回), and period-end net assets (期末净资产), in shares and CNY. Answers '基金份额变动', 'ETF shares outstanding history', '515050规模变动', 'how many shares outstanding does this ETF have over time'. IMPORTANT: this is NOT a daily series, Chinese ETFs publicly disclose 份额 only at quarter-end plus occasional ad-hoc material-change dates (confirmed live for 515050/561980/588170/588200), not every trading day; a from/to window with no disclosure inside it returns found:false naming the nearest disclosed dates rather than fabricating daily rows. For a daily PRICE series use ashares_daily_history; this tool is share-count/AUM only. Source: Eastmoney fund F10 archive (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": {
      "code": "515050"
    },
    "name": "ashares_etf_shares"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLatest disclosure date to include, YYYY-MM-DD or YYYYMMDD (inclusive). Default: today (no upper bound in practice).
codeYes6-digit ETF code, e.g. "515050", "561980", "588170", "588200", or "512000".
fromNoEarliest disclosure date to include, YYYY-MM-DD or YYYYMMDD (inclusive). Default: no lower bound (full history, newest first, capped).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower, but the description still adds real behavioral context: quarter-end-plus-ad-hoc disclosure cadence, no daily fabrication, and a found:false response naming nearest disclosed dates. It also discloses the keyless Eastmoney F10 source. The main remaining gap is the result ordering/capping behavior, which is only mentioned indirectly via the schema's 'newest first, capped'.

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 fields, then the important caveat, then the alternative and source. It is a dense single paragraph but nearly every clause carries information; the query-phrase examples are slightly redundant with the field list but still aid matching.

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 no output schema, the description still covers what is returned (shares, subscriptions/redemptions, net assets in CNY) and how failure looks (found:false with nearest dates). For a 3-parameter read-only tool with full schema coverage, nothing an agent needs in order to 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 coverage is 100%, so the baseline is 3; the description goes beyond it by explaining what a from/to window with no disclosure inside it does (returns found:false with nearest dates). That is meaningful semantics for the date parameters that the schema alone does not convey.

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?

The description names a specific resource (ETF fund-share-count and net-asset history) and enumerates the exact returned fields with Chinese terms (期末总份额, 期间申购/赎回, 期末净资产) plus units. It also explicitly contrasts with ashares_daily_history, so an agent can pick it apart from siblings without opening a 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?

It states when to use this tool (share-count/AUM questions), gives sample natural-language queries, and names the alternative (ashares_daily_history) for the case it does not cover, i.e. daily price series. The exclusion is explicit rather than implied.

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.