Skip to main content
Glama

Udi Recent Changes

udi_recent_changes
Read-onlyIdempotent

Devices in China's medical-device UDI register whose latest published version is on or after a given date, newest first — drawn from the publisher's delta (daily/weekly/monthly) release files.

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": 3,
      "since": "2026-10-27"
    },
    "name": "udi_recent_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows to return (default 50, max 100)
sinceYesISO date (YYYY-MM-DD) — list devices versioned on or after this date (at most 90 days before the latest release)

Output Schema

NameRequiredDescriptionDefault
countNo
sinceNo
sourceNo
changesNo
data_as_ofNo
total_changed_sinceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely new context: results come from the publisher's daily/weekly/monthly delta files and are ordered newest first, which tells the agent how the data is produced and sorted. It stops short of noting the 90-day lookback cap, which lives only in the schema.

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?

A single dense sentence with the scope, ordering, and data source front-loaded and zero filler. Every clause carries information an agent needs.

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 an output schema present, return values need not be explained, and annotations cover safety. The description supplies scope, ordering, and provenance, leaving only minor gaps such as the 90-day window and pagination behavior, both of which the schema handles.

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, since) are already fully documented including defaults, max, and the 90-day bound. 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.

Purpose4/5

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

States a specific verb+resource: devices in China's medical-device UDI register whose latest published version falls on/after a date, newest first, sourced from delta release files. That is far more precise than the title. It does not, however, contrast itself with siblings such as udi_search or recent_changes, so an agent must infer the boundary.

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

Usage Guidelines3/5

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

The 'recent changes / delta release' framing implies a monitoring or incremental-sync use case, but the description never says when to prefer this over udi_search or the generic recent_changes, nor any exclusions. Usage is implied rather than stated.

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.