Skip to main content
Glama

China Exchange Data

Ashares Bulletins

ashares_bulletins
Read-onlyIdempotent

上交所上市公司公告, SSE-listed company disclosure bulletins (公告) by 6-digit code: title, type (半年报/年报/董事会/股东会/回购/关联交易 etc.), date, and the PDF URL on the CNINFO disclosure platform. Answers "600519最新公告", "贵州茅台公司公告", "SSE company bulletins since 2026-01-01", "annual report / 年报 filings for a code". SZSE-listed codes (0/3-prefixed) are not covered, this tool is SSE-only. Source: CNINFO (巨潮资讯网), the CSRC-designated disclosure platform (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": "600519",
      "limit": 8,
      "since": "2026-01-01"
    },
    "name": "ashares_bulletins"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes6-digit SSE code, e.g. "600519" (贵州茅台).
typeNoFilter by bulletin type substring, e.g. "年报" or "股东会" (default: all types).
limitNoMax bulletins to return, 1-100 (default 20, newest first). The response always reports the true total on file.
sinceNoOnly return bulletins on or after this date, YYYY-MM-DD (default: no lower bound, most recent first).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / since / description
      Previous value: -"Only return bulletins on or after this date, YYYY-MM-DD (default: no lower bound — most recent first)."New value: +"Only return bulletins on or after this date, YYYY-MM-DD (default: no lower bound, most recent first)."
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, non-destructive, so the safety profile is covered. The description adds genuinely useful non-schema context: keyless access, CNINFO as the CSRC-designated source, and that the PDF URL originates there. It stops short of stating pagination/ordering behavior or error behavior for invalid codes, so it only modestly exceeds the annotation bar.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and returned fields are front-loaded in the opening clause, followed by retrieval-friendly example queries, then scope limits and provenance. Every sentence carries information an agent would use; nothing is redundant with the title or schema.

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?

With no output schema, the description carries the return-value burden and does so by naming the fields returned and the CNINFO provenance. Coverage limits (SSE-only), the keyless source, and default ordering in the schema together make it callable without guesswork; only error/empty-result behavior is left unstated.

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 four parameters are already documented, establishing a baseline of 3. The description does add a broader enumeration of type values (半年报/年报/董事会/股东会/回购/关联交易) than the schema's two examples, which helps construct filters, but it does not add syntax or format detail for code/since/limit.

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+resource ('SSE-listed company disclosure bulletins (公告) by 6-digit code') and enumerates the returned fields (title, type, date, PDF URL). It also bounds scope explicitly by declaring SZSE 0/3-prefixed codes out of scope, so an agent can tell immediately whether this is the right tool.

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 example queries ('600519最新公告', 'annual report / 年报 filings for a code') that map user phrasings to this tool, plus an explicit exclusion for SZSE codes. It does not name an alternative tool for the SZSE case, so the routing guidance is clear on when-to-use but not on where-to-go-instead.

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.