Skip to main content
Glama

eudamed_udi_di_validator

Read-onlyIdempotent

[EUDAMED Basic UDI-DI & UDI-DI / PI GS1 modulo-10 barcode validator. Pure calculation, read-only, side-effect free]. Audits Basic UDI-DI and UDI-DI / UDI-PI structures under Regulation (EU) 2017/745 Article 27 and Implementing Regulation (EU) 2021/1239, verifying GS1 GTIN-14 modulo-10 check digits and production identifiers. Usage: Pass agency, Basic UDI-DI, and UDI-DI/PI strings to audit EUDAMED registration readiness and format human-readable text. Returns: JSON object with { issuingAgency: string, basicUdiDi: string, isBasicUdiDiValid: boolean, udiDi: string, isUdiDiValid: boolean, udiDiCheckDigitCalculated: number, udiPiElementsPresent: array, eudamedRegistrationReady: boolean, statutoryVerdict: string, formattedHumanReadableRepresentation: string }.

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": {
      "issuingAgency": "<issuingAgency>",
      "basicUdiDi": "<basicUdiDi>",
      "udiDi": "<udiDi>"
    },
    "name": "eudamed_udi_di_validator"
  }
}

Input Schema

NameRequiredDescriptionDefault
udiDiYesUDI-DI static device identifier (e.g. 14-digit GTIN for GS1)
basicUdiDiYesBasic UDI-DI (Model identifier registered in EUDAMED)
issuingAgencyYesDesignated UDI issuing agency ex Commission Implementing Decision (EU) 2019/939
udiPiLotNumberNoBatch/Lot number production identifier (AI 10)
udiPiSerialNumberNoSerial number production identifier (AI 21)
udiPiSoftwareVersionNoSoftware identification version for SaMD (AI 8012)
udiPiExpirationDateYymmddNoExpiration date in YYMMDD format (AI 17)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, and the description reinforces this with 'Pure calculation, read-only, side-effect free', so the safety profile is consistent rather than contradictory. It further discloses the full return shape (validity flags, calculated check digit, PI elements present, registration-ready verdict, human-readable string), which matters because no output schema exists. It stops short of describing failure modes, e.g. how HIBCC/ICCBBA/IFA inputs are handled versus GS1 modulo-10.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Structure is strong: bracketed scope, Usage, then Returns, so the agent can skim to the needed section. The long inline return-type listing is verbose but earns its place given the absence of an output schema; only the statutory citations are arguably redundant.

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 7-parameter, 3-required validation tool with no output schema and no nesting, the definition covers purpose, inputs, statutory basis and every return field. The main gap is coverage of the non-GS1 issuing agencies in the enum, which the description never addresses.

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 the schema already documents all seven parameters including AI codes for lot, serial, software version and expiration date. The description adds only the GS1 GTIN-14 modulo-10 rationale and the notion of 'production identifiers', which does not meaningfully extend the required-field or enum semantics. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

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

States a specific verb and resource: it validates EUDAMED Basic UDI-DI and UDI-DI/UDI-PI structures against Regulation (EU) 2017/745 Art. 27 and Implementing Regulation (EU) 2021/1239. The bracketed opener and the statutory framing make the scope unambiguous and clearly distinct from the other validator siblings.

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 'Usage' line tells the agent which inputs to pass and what the audit is for (EUDAMED registration readiness plus human-readable formatting), which implies when to reach for it. However, there is no explicit when-not guidance, no mention of alternatives, and no statement of what happens for non-GS1 issuing agencies despite the four-value enum.

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.

Resources