Skip to main content
Glama

check_udi

Validates a 14-digit UDI-DI and returns classification, sterile, and single-use attributes; if no match, explains sample-data coverage without implying the real database lacks the code.

Instructions

校验 14 位 UDI-DI 并回出分类/无菌/一次性属性。未命中会说明示例数据范围,不代表真实数据库无此编号。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "udi_di": "<udi_di>"
    },
    "name": "check_udi"
  }
}

Input Schema

NameRequiredDescriptionDefault
udi_diYes14 位 UDI-DI

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does meaningful work: it discloses that the tool validates format, returns three derived attributes, and — importantly — that a miss explains the sample-data scope rather than proving the code is absent from the real database. That negative-result caveat is genuinely useful behavioral context. It stops short of covering malformed-input behavior (e.g., a 13-digit string) or distinguishing format-invalid from not-found responses.

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 tight sentences: purpose plus return values first, then the caveat about miss interpretation. Every clause carries information and nothing is redundant — notably compact given the language.

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 lookup with no output schema and no annotations, the description compensates well by enumerating the returned attributes and explaining negative results. The only real gap is what happens on structurally invalid input, which matters for a format-sensitive validator.

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?

There is a single required parameter with 100% schema description coverage, so the schema already defines 'udi_di' as a 14-digit UDI-DI. The description restates the same '14 位' constraint without adding format examples, checksum rules, or normalization behavior, so it adds no meaning beyond the schema. 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 names a specific verb+resource (validate a 14-digit UDI-DI) and states exactly what comes back: classification, sterility, and single-use attributes. No sibling tool (check_timeline, calc_quote, match_labs, etc.) overlaps this resource, so the operation is unambiguous even though no alternative is explicitly named.

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 explicit statement of when to call this versus another tool, no prerequisites, and no guidance on what to do if the caller has only a partial or non-14-digit code. Usage is only inferable from the stated purpose, and the miss-handling note describes outcomes rather than when-to-use conditions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.