Skip to main content
Glama

Nmpa Updates

nmpa_updates
Read-onlyIdempotent

Official announcements from China's drug regulator, the NMPA (National Medical Products Administration), regulatory policy changes, guidance documents, import rules, clinical-trial guideline updates and reform opinions, in English, straight from the regulator. Answers "latest NMPA regulatory updates", "what has China's drug regulator changed", "NMPA guidance on medical devices or cosmetics". Returns title, publication date and the announcement URL. NOTE: this is the announcements feed, NOT the drug-approval register, it does not list which drugs were approved.

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": {
      "limit": 15
    },
    "name": "nmpa_updates"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum announcements, 1-40 (default 15).
sectionNoLimit to one section. Omitted, all four are merged and sorted newest first.

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?

With readOnlyHint, idempotentHint, openWorldHint and destructiveHint already declared, the description's extra value is that results are in English, sourced straight from the regulator, and default to all four sections merged newest-first. It also discloses the shape of the returned records. It stops short of covering freshness, pagination beyond the limit cap, or how items are deduplicated across sections.

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?

The core purpose is front-loaded, the example queries follow, and the corrective NOTE is placed last where it is most likely to be read as a caveat. The topic enumeration is somewhat long but each item is a concrete coverage claim 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?

There is no output schema, yet the description says what each record contains (title, date, URL), states the language, and rules out the most likely misidentification. For a two-parameter, optional-only read tool this is everything an agent needs to call it correctly.

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 both parameters (limit with its 1-40 range, section enum) are already fully documented. The description adds only the merged-across-sections behavior, which the schema already states. Baseline 3 applies since the schema carries the parameter burden.

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 (official announcements from China's NMPA) and enumerates the content types it carries: regulatory policy changes, guidance documents, import rules, clinical-trial guideline updates and reform opinions. It also states the output fields (title, publication date, URL), so an agent knows exactly what it gets back.

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 provides concrete trigger queries ("latest NMPA regulatory updates", "what has China's drug regulator changed", "NMPA guidance on medical devices or cosmetics") and an explicit exclusion: this is the announcements feed, NOT the drug-approval register, and does not list approved drugs. That exclusion does the routing work against the nmpa_drug_approval siblings without needing to name them.

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.