Skip to main content
Glama

Cninfo Disclosure Search

cninfo_disclosure_search
Read-onlyIdempotent

Full-text search over CNINFO (cninfo.com.cn), the official disclosure feed for BOTH Chinese A-share exchanges, Shenzhen (SZSE) and Shanghai (SSE), STAR Market (科创板) included. Covers A-share-listed companies with zero HK or US nexus, the deals and IPOs invisible to every SEC- or HKEX-based tool in this catalog (a China-to-China licensing deal, or a STAR Market IPO prospectus). Answers "A股许可协议公告" (A-share licensing announcements), "STAR Market IPO prospectus filings", "科创板 招股说明书". Search terms must be Chinese (e.g. "许可" for licensing/approval disclosures, "招股说明书" for IPO prospectuses), do not translate an English query and search that. Optionally filter to one verified board segment (board). Returns company, stock code, title, date and PDF link, plus the true total match count.

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": {
      "query": "许可"
    },
    "name": "cninfo_disclosure_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
boardNoRestrict to one verified board segment: "star" = STAR Market (科创板, SSE, all 688xxx codes) or "chinext" = ChiNext (创业板, SZSE). Omit to search all SZSE+SSE boards.
limitNoMaximum disclosures to return, 1-40 (default 15).
queryYesChinese-language search term, e.g. "许可" (license/licensing) or "招股说明书" (IPO prospectus). Required.
sinceNoEarliest disclosure date, YYYY-MM-DD. Omitted, no lower bound (server-side date filter, genuinely narrows results).
untilNoLatest disclosure date, YYYY-MM-DD. Defaults to today. Only applied when `since` is also set.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description adds value beyond that by stating the return payload (company, stock code, title, date, PDF link) and that the true total match count is returned rather than just the page size — a real behavioral detail. It does not mention rate limits, latency, or auth/open-web scraping caveats, so it falls short of a 5.

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 scope before the query-language constraints, and every sentence carries information an agent needs (coverage, exclusions, language rule, return fields). Slightly verbose in the parenthetical restatement of SZSE/SSE and the bilingual glosses, but nothing is filler.

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?

Five parameters at full schema coverage plus a description that lists return fields means an agent can call this without guessing. What is missing is peripheral but real: no note on paging beyond the limit cap, on result ordering, or on failure modes when the Chinese term yields nothing.

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, and the description still adds operational meaning: the query must be Chinese with examples ('许可' for licensing, '招股说明书' for prospectuses) plus the explicit warning against translating an English query. The board filter is described as restricting to 'one verified board segment', clarifying that it cannot broaden scope, though date-filter interaction is left entirely to the schema.

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 ('Full-text search over CNINFO') and pins the scope precisely: the official disclosure feed for SZSE and SSE, STAR Market included, with 'zero HK or US nexus'. That scope statement makes it immediately distinguishable from SEC/HKEX disclosure tools in the catalog.

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 an explicit when-to-use signal (A-share deals and IPOs 'invisible to every SEC- or HKEX-based tool'), concrete query examples in Chinese, and a hard rule not to translate English queries and search those. It also names the condition for the optional board filter and what happens when it is omitted.

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.