Skip to main content
Glama

Nmpa Drug Approvals

nmpa_drug_approvals
Read-onlyIdempotent

NMPA (国家药监局) drug-APPROVAL events, a specific drug cleared for marketing, granted conditional approval, or given an expanded indication in China, as opposed to nmpa_updates, which is regulatory policy news. 批准 新药 创新药 获批上市 NMPA新药批准. Answers "latest NMPA drug approvals in China", "2026年8月NMPA批准的新药", "what new drugs did China approve this month", "recent Chinese biotech drug approvals". Sourced from HKEX (Hong Kong Exchange) disclosure filings: any Hong Kong-listed biotech announces an NMPA approval as a regulatory disclosure the same day, and that filing is public and structured. Returns the filing headline (which names the drug and often the indication), the company, the approval date, a best-effort category, and the filing PDF. Coverage is limited to HKEX-listed companies, see coverage_note in the response.

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": {
      "month": "2026-08"
    },
    "name": "nmpa_drug_approvals"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum approvals to return, 1-40 (default 15).
monthNoA single month, "YYYY-MM" (e.g. "2026-08"). Takes priority over since/until.
queryNoFilter to filings whose headline or company name contains this text (drug name, code like "TY-9591", or company like "HUTCHMED").
sinceNoEarliest approval date, YYYY-MM-DD. Ignored if `month` is set.
untilNoLatest approval date, YYYY-MM-DD. Ignored if `month` is set.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), yet the description adds genuinely non-obvious behavior: the data source is HKEX disclosure filings, coverage is limited to HKEX-listed companies with a coverage_note in the response, and the category field is best-effort. That coverage caveat is the most important thing an agent could misjudge, and it is disclosed. Minor gap: no note on update latency or how far back history goes.

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?

Purpose and sibling differentiation are front-loaded, and the keyword block plus example queries aid retrieval matching. It is somewhat repetitive — four example queries and a Chinese keyword list restate the same intent — but the length is justified by the domain aliasing rather than filler.

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?

No output schema exists, so the description carries the return-value burden and does so: filing headline naming drug and indication, company, approval date, best-effort category, and filing PDF. Combined with the source and coverage constraint, an agent has everything needed to call it correctly and to caveat the results.

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 five parameters (limit, month, query, since, until) and their precedence rules are already documented in structured data. The description adds no additional syntax or semantics beyond what the schema states; 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 resource and event type — NMPA drug-approval events: marketing clearance, conditional approval, expanded indication in China — and explicitly contrasts it with the sibling nmpa_updates (regulatory policy news). An agent can distinguish the two without opening either 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?

Gives an explicit negative case (not policy news -> nmpa_updates) and several concrete user-phrasings it should answer ("latest NMPA drug approvals in China", "what new drugs did China approve this month"), which maps intent to tool unambiguously. The domain boundary is stated, not 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.