Skip to main content
Glama

Udi Resolve

udi_resolve
Read-onlyIdempotent

Resolve one China medical-device Unique Device Identifier (UDI-DI) to its registered product record — name, model, classification, registrant, and registration number.

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": {
      "udi_di": "06941862700094"
    },
    "name": "udi_resolve"
  }
}

Input Schema

NameRequiredDescriptionDefault
udi_diYesThe product-level UDI-DI to resolve

Output Schema

NameRequiredDescriptionDefault
foundNo
modelNo
sourceNo
udi_diNo
name_cnNo
categoryNo
data_as_ofNo
registrantNo
trade_nameNo
descriptionNo
ingested_atNo
version_timeNo
version_numberNo
version_statusNo
first_publishedNo
classification_codeNo
registration_numberNo

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 readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety and determinism profile is fully covered. The description adds only that the target is the China registry and a registered product record, plus the field list — which duplicates the output schema rather than adding behavior like not-found handling or rate limits.

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 front-loaded sentence that identifies the input, the transformation, and the returned content with no filler. Every clause carries information; nothing is redundant or buried.

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?

For a one-parameter, read-only resolution tool with rich annotations and an output schema, the description covers what the tool consumes and produces. The main residual gap is failure semantics — behavior when the UDI-DI is not found in the Chinese registry — which an agent would benefit from knowing.

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?

With a single required parameter at 100% schema description coverage, the schema already documents 'udi_di' and supplies an example value (06941862700094). The description adds no format guidance (e.g., expected digit length or whether packaging-level UDI-DIs are accepted), so it does not exceed the schema baseline.

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 ('Resolve') and resource (China medical-device UDI-DI -> registered product record), and enumerates the returned fields (name, model, classification, registrant, registration number). The singular framing ('one') hints at the distinction from a sibling like udi_search, but no sibling is named explicitly, so differentiation is implied rather than stated.

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 only implied: resolving a single known UDI-DI to its product record. There is no statement of when to prefer this over udi_search or udi_manufacturer, and no mention of what happens if the identifier is unknown or malformed. Adequate for a simple lookup, but an agent gets no explicit routing rule.

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.