Skip to main content
Glama

LexGrid EU MDR Medical Devices & Pharma Serialization MCP

Falsified Medicines Directive (FMD) 2D DataMatrix Serialization Auditor

fmd_pharma_serialization_matrix_auditor
Read-onlyIdempotent

[Falsified Medicines Directive (FMD) 2D DataMatrix serialization auditor. Pure calculation & parsing, read-only, side-effect free]. Audits medicinal product safety features under Directive 2011/62/EU and Delegated Regulation (EU) 2016/161, validating GTIN-14 check digits, randomized serial numbers (<1:10,000 entropy), expiration dates, and anti-tampering seals. Usage: Pass pharmaceutical packaging identifiers to verify compliance with EMVS European Hub serialization standards. Returns: JSON object with { medicinalProductName: string, isSerializationCompliant: boolean, gtinCheck: object, serialNumberCheck: object, expirationDateCheck: object, antiTamperingDeviceAudit: object, emvsPayloadRepresentation: object, deficiencies: array }.

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": {
      "medicinalProductName": "<medicinalProductName>",
      "marketingAuthorisationHolder": "<marketingAuthorisationHolder>",
      "gtinOrNtin14Digits": "<gtinOrNtin14Digits>",
      "serialNumber": "<serialNumber>",
      "batchOrLotNumber": "<batchOrLotNumber>",
      "expirationDateYymmdd": "<expirationDateYymmdd>",
      "antiTamperingDevicePresent": "<antiTamperingDevicePresent>"
    },
    "name": "fmd_pharma_serialization_matrix_auditor"
  }
}

Input Schema

NameRequiredDescriptionDefault
serialNumberYesRandomized serial number (8-20 alphanumeric characters, guessing probability < 1:10,000)
batchOrLotNumberYesManufacturing batch / lot identifier
gtinOrNtin14DigitsYes14-digit Global Trade Item Number (GTIN) or National Trade Item Number (NTIN)
expirationDateYymmddYesExpiration date in 6-digit YYMMDD format
medicinalProductNameYesOfficial proprietary or generic name of the medicinal product for human use
nationalReimbursementTypeNoType of national reimbursement code format
antiTamperingDevicePresentYesWhether packaging incorporates an Anti-Tampering Device (ATD) ex Art. 54a(2)(b)
nationalReimbursementNumberNoNational reimbursement or identification code where required by Member State (e.g. AIC, CIP, PZN)
marketingAuthorisationHolderYesName of Marketing Authorisation Holder (MAH) established in EU

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, and the description reinforces this as 'pure calculation & parsing, side-effect free' — partly redundant but harmless. It goes beyond the annotations by disclosing the actual validation criteria applied (check-digit verification, serial entropy threshold, ATD audit) and by sketching the returned JSON keys, which matters since no output schema exists. It does not cover error behavior for malformed input or any rate/permission considerations, which is a minor omission for a pure calculator.

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?

The bracketed lead, then scope, then Usage, then Returns is a clean front-loaded structure with no filler sentences. The inline Returns enumeration is dense and partially duplicates what the schema-level checks already imply, which costs a point but is defensible given no output schema exists.

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 9-parameter, 7-required compliance tool with no output schema, the description does the necessary extra work: it states the legal basis, the checks performed, and the shape of the response including a deficiencies array. Gaps remain around the conditional national reimbursement fields and what constitutes a failing versus inconclusive result, but the core is complete enough for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3; the description earns an extra point by tying parameters to their compliance semantics — GTIN-14 check-digit validation, serial number entropy below 1:10,000, YYMMDD expiration format, and ATD presence per Art. 54a(2)(b). The five non-required fields (national reimbursement type/number, etc.) are never mentioned in the description, leaving their role explained only by the schema.

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?

The description names a specific verb-resource pair — auditing medicinal product safety features under Directive 2011/62/EU and Delegated Regulation (EU) 2016/161 — and enumerates exactly what is checked (GTIN-14 check digits, randomized serials with <1:10,000 entropy, expiration dates, anti-tampering seals). An agent can tell immediately this is an FMD/EMVS serialization compliance validator, which is distinct from every listed sibling domain.

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 says to pass pharmaceutical packaging identifiers to verify EMVS compliance, which implies the calling context but states no trigger conditions, prerequisites, or exclusions. There is no guidance on when this tool is the wrong choice versus a general validator, and no note on whether incomplete packaging data should be sent anyway.

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