Skip to main content
Glama

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. Added

TDQS

A4.1/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 with 'pure calculation & parsing, side-effect free', adding that no external hub call is made. It also enumerates the return payload fields, which matters because no output schema exists. It stops short of describing failure modes or how deficiencies are populated.

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?

Three labeled segments (scope bracket, Usage, Returns) front-load the regulatory domain and the check list before the mechanics. Dense but every clause carries information; only the bracketed read-only restatement is mildly redundant with annotations.

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 validator with no output schema, the description covers the domain, the checks performed, and the shape of the returned JSON, which is what an agent needs to invoke and interpret it. Only edge-case behavior (e.g., what happens on malformed GTIN or missing reimbursement code) is left unstated.

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 all nine parameters including the required GTIN, serial, YYMMDD expiration and ATD flag are documented in the schema itself. The description only echoes one of these constraints (the <1:10,000 serial entropy threshold) and adds no format or validation detail the schema does not already carry, so the 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 domain verb and resource: auditing FMD 2D DataMatrix safety features under Directive 2011/62/EU and Delegated Regulation (EU) 2016/161, and enumerates the four checks performed (GTIN-14 check digit, randomized serial, expiration date, anti-tampering seal). An agent can distinguish this pharma serialization validator from the compliance siblings (einvoice, CLP, CBAM, DPP) without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'Usage' line establishes the conditional context clearly: pass pharmaceutical packaging identifiers to verify compliance against EMVS European Hub standards, which scopes the tool to EU medicinal products. It gives no explicit exclusions or named alternatives, but the regulatory framing is narrow enough that misfiling is unlikely.

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