Skip to main content
Glama

Udi Search

udi_search
Read-onlyIdempotent

Search China's medical-device Unique Device Identification register by product name, trade name, or model, refreshed from the publisher's release files. Optionally filter by registrant (manufacturer) name.

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,
      "query": "起搏器",
      "manufacturer": "美敦力"
    },
    "name": "udi_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows to return (default 20, max 100)
queryYesProduct name, trade name, or model keywords (space-separated terms, all must match)
manufacturerNoOptional registrant/manufacturer name filter (Chinese or English)

Output Schema

NameRequiredDescriptionDefault
countNo
queryNo
sourceNo
resultsNo
data_as_ofNo
manufacturerNo
matches_cappedNo
candidates_consideredNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/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 real value beyond that with data provenance ('refreshed from the publisher's release files') and a hard geographic scope limit (China only), which prevents an agent from assuming global coverage. It stops short of describing result ordering, truncation behavior, or what an empty match set looks like.

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, front-loaded with the resource and scope, then the optional filter. No filler, no restatement of the title, and every clause carries information an agent would otherwise have to guess at.

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?

An output schema exists, so return values need not be explained, and all three parameters are fully documented. With annotations covering the safety profile, the only missing piece for a search tool of this complexity is guidance on result ordering or paging beyond the limit cap and on picking among the sibling udi_* lookups.

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%, with each parameter already documented including space-separated AND semantics and the default/max for limit, so the baseline is 3. The description restates the same field list without adding syntax, format, or ranking details beyond the schema.

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?

Names a specific verb (search) and resource (China's medical-device UDI register) and enumerates the searchable fields: product name, trade name, model, plus an optional registrant filter. It does not contrast itself with the similarly prefixed siblings (udi_manufacturer, udi_resolve, udi_coverage), so an agent must infer which of those to prefer, but the operation itself is unambiguous.

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 word 'Optionally' clarifies that manufacturer is a refinement rather than a requirement, which gives implicit guidance on how to shape a query. There is no explicit when-to-use versus when-not guidance, no mention of what to do when results are empty, and no routing to the other udi_* tools.

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.