Skip to main content
Glama

Udi Manufacturer

udi_manufacturer
Read-onlyIdempotent

Look up a medical-device registrant (manufacturer) in China's UDI register by name or unified social credit code, and see how many device identifiers and registration numbers it holds.

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": "迈瑞",
      "limit": 3
    },
    "name": "udi_manufacturer"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoRegistrant name (Chinese or English), partial match; short names such as 联影 work
limitNoMax registrants to return (default 10, max 50)
registrant_idNoRegistrant's unified social credit code (统一社会信用代码), exact match

Output Schema

NameRequiredDescriptionDefault
countNo
queryNo
sourceNo
data_as_ofNo
registrantsNo

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?

The annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds a little context by framing the result as aggregate counts of identifiers and registration numbers, but says nothing about match behavior beyond the schema's partial-match note, empty results, or ordering.

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?

One front-loaded sentence of roughly 30 words that states the action, the data source, the lookup keys, and the shape of the answer, with no filler or redundancy.

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 and full parameter coverage, the description needs only to establish identity and inputs, which it does. It falls short of complete only because it never situates the tool relative to its UDI siblings, leaving the agent to guess which lookup to call.

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%, including the unified social credit code's exact-match semantics and even a partial-match example for name, so the schema does the heavy lifting. The description only restates the two lookup modes, adding no syntax or format detail beyond the structured fields; 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?

The description uses a specific verb and resource ('Look up a medical-device registrant ... in China's UDI register') and states the two lookup keys, so an agent knows exactly what is retrieved. It does not, however, distinguish this from the sibling registrant/device lookups (udi_search, udi_resolve), which is the main gap for a 4 rather than a 5.

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?

Usage is implied by naming the two accepted keys (name or unified social credit code) and by the registrant-level view it returns ('how many device identifiers and registration numbers it holds'). There is no explicit statement of when to prefer this over udi_search or udi_resolve, and no prerequisites or exclusions are given.

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.