Skip to main content
Glama

Udi Coverage

udi_coverage
Read-onlyIdempotent

Coverage of China's medical-device UDI register: device count, the full release and latest delta applied, and the data_as_of date. Registrant identity is withheld for individual (natural-person) registrants.

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": "udi_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
sourceNo
devicesNo
data_as_ofNo
ingested_atNo
full_releaseNo
newest_versionNo
releases_appliedNo
latest_release_appliedNo
registrant_identity_withheld_for_individualsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint), so the bar is lower. The description adds genuine context beyond them: registrant identity is withheld for natural-person registrants, which tells the agent why individual-level attribution may be missing. It still does not state refresh cadence or what a stale data_as_of implies for downstream queries.

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?

Two sentences, no filler, and the payload (what is returned) is front-loaded ahead of the privacy caveat. Every clause carries information an agent would otherwise have to guess.

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 parameters, an output schema present, and full annotation coverage, the definition only needs to explain what the numbers mean and any caveats. It does that, including the withheld-identity note. The one omission is situational placement relative to the other udi_* tools, which keeps it off a 5.

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?

The tool takes zero parameters, so there is no parameter meaning to convey and the baseline of 4 applies. The description correctly avoids inventing arguments and instead spends its text on the shape of the response.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (China's medical-device UDI register) and enumerates exactly what it reports: device count, the full release and latest delta applied, and data_as_of. That is far more concrete than 'get coverage'. It does not, however, explicitly contrast itself with siblings like udi_search or udi_recent_changes, so an agent must infer that this is the dataset-level metadata call rather than a lookup.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance: nothing says this is the call to make first to check data freshness or register size before running udi_search, nor that it returns no device rows. The agent must derive the usage pattern purely from the described return fields.

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.