Skip to main content
Glama

Csrc Penalties

csrc_penalties
Read-onlyIdempotent

Administrative penalty decisions (行政处罚决定书) from the CSRC, the China Securities Regulatory Commission, China's securities and capital-markets regulator, newest first, straight from csrc.gov.cn's own JSON feed. Each row carries the decision number (e.g. 〔2026〕42号), the publication date, the named parties from the decision's opening lines (listed companies, accounting firms, individuals sanctioned for disclosure fraud, insider trading, market manipulation), and the link to the full decision. Answers "recent CSRC enforcement actions", "中国证监会最近的行政处罚", "which companies did China's securities regulator penalize". This is securities-market enforcement, not drug regulation, for NMPA announcements use nmpa_updates.

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": {},
    "name": "csrc_penalties"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 1-based (default 1). Pages are newest-first.
limitNoRows per page, 1-40 (default 15).
sinceNoEarliest publication date, YYYY-MM-DD. Omitted, the newest decisions are returned regardless of age.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds useful context beyond that: results are newest-first, sourced directly from csrc.gov.cn's JSON feed, and each row includes decision number, publication date, named parties, and a link to the full decision.

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-loads the resource and source, then the returned fields, then the disambiguation. It is somewhat dense and long, but nearly every clause carries information an agent needs; the parenthetical examples of sanctioned party types are the only mild padding.

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?

For a read-only, three-optional-parameter list tool with no output schema, the description covers source, ordering, returned fields, and sibling disambiguation. 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.

Parameters3/5

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

Schema description coverage is 100%, so page, limit and since are already fully documented, including the newest-first ordering and the since-omitted behavior. The description adds no parameter-level detail beyond what the schema provides, so the 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+resource (administrative penalty decisions from the CSRC), gives the Chinese term, the source domain, and explicitly distinguishes itself from nmpa_updates as securities enforcement rather than drug regulation. An agent can identify this tool without opening the schema.

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?

Provides concrete example queries it answers ('recent CSRC enforcement actions', 'which companies did China's securities regulator penalize') and an explicit exclusion routing drug-regulation queries to nmpa_updates. It does not cover other possible alternatives, but the when-to-use context is clear.

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.