Skip to main content
Glama

TracePass

by eu.tracepass
OverviewDiscussionsAdmin

TracePass passport parties

tracepass_passport_parties
Idempotent

Manage the economic-operator parties on a passport — manufacturer, importer, authorisedRepresentative, distributor, recycler, producerResponsibilityOrg. Each party carries a legal name and at least one identifier.

Identifier rules (EN 18219 §6.2–6.5): a party needs at least one of gln, legacyOperatorId, or operatorIdentifier. If both gln and operatorIdentifier (scheme gln) are provided they must agree — a mismatch returns 400. An operatorIdentifier of scheme gln also fills the top-level gln field; facilityIdentifier never does. Typed identifiers (operatorIdentifier / facilityIdentifier) are not set by AI extraction or CSV import.

operatorIdentifier schemes: • iso6523 — { scheme:"iso6523", icd:"<4 digits>", value } — ICD 0199 = LEI (ISO 17442), 0088 = GLN, 0060 = DUNS. • gln — { scheme:"gln", gln:"<13 digits>" } — also fills top-level gln. • did — { scheme:"did", did:"did::" } — syntax-checked only (EN 18219 §6.4.2(b)). • doi — { scheme:"doi", doi:"10./" } — doi:/https://doi.org/ prefix accepted and stripped.

facilityIdentifier schemes: same four; the gln variant also accepts optional extension (GS1 SGLN sub-location).

Actions (pass via action, with args):

  • set — args: { id, role, legalName, gln?, country?, legacyOperatorId?, operatorIdentifier?, facilityIdentifier? }. Sets or updates one role.

  • remove — args: { id, role }. Clears one role.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argsNoArguments for the chosen action; required fields depend on `action`.
actionYesSet (add/replace) or remove an economic-operator party on a passport by its role.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoThe resource's TracePass id, when the response is a single entity.
pageNoCurrent page number (list actions).
errorNoMachine-readable error code, when the API rejected the request.
itemsNoThe page of results, when the action is a list.
limitNoPage size (list actions).
totalNoTotal matching records across all pages (list actions).
resultNoWraps a non-object response body (e.g. a QR code string).
messageNoHuman-readable error or status detail, when present.
totalPagesNoTotal number of pages (list actions).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / args / properties / country / description
      Previous value: -"Party country code (set, optional)."New value: +"ISO 3166-1 alpha-2 country code (set, optional)."
    • addedInput schema / properties / args / properties / facilityIdentifier
      Added value: +{
+  "additionalProperties": {},
+  "description": "Structured facility identifier per EN 18219 §6.2–6.5. Same four schemes as operatorIdentifier; the gln variant also accepts optional `extension` (GS1 SGLN sub-location). Never fills the top-level gln field. Not set by AI extraction.",
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}
    • changedInput schema / properties / args / properties / gln / description
      Previous value: -"GS1 Global Location Number for the party (set, optional)."New value: +"GS1 Global Location Number (13 digits). Strongly recommended for multi-role disambiguation."
    • changedInput schema / properties / args / properties / legacyOperatorId / description
      Previous value: -"Your internal operator id for the party (set, optional)."New value: +"Free-text fallback identifier (VAT, EORI, supplier code). Required when gln and operatorIdentifier are both absent."
    • addedInput schema / properties / args / properties / operatorIdentifier
      Added value: +{
+  "additionalProperties": {},
+  "description": "Structured operator identifier per EN 18219 §6.2–6.5. Must have `scheme` plus scheme fields. Schemes: iso6523 {icd:\"<4 digits>\", value} | gln {gln:\"<13 digits>\"} | did {did:\"did:<method>:<id>\"} | doi {doi:\"10.<registrant>/<suffix>\"}. scheme gln also fills the top-level gln field; they must match if both are set (400 otherwise). Not set by AI extraction.",
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}
    • changedInput schema / properties / args / properties / role / description
      Previous value: -"Economic-operator role, e.g. manufacturer | importer | distributor | authorised_representative (required)."New value: +"Economic-operator role: manufacturer | importer | authorisedRepresentative | distributor | recycler | producerResponsibilityOrg (required)."
  2. Changed6 schema fields changed
    • addedInput schema / properties / action / description
      Added value: +"Set (add/replace) or remove an economic-operator party on a passport by its role."
    • removedInput schema / properties / args / additionalProperties
      Removed value: -{}
    • changedInput schema / properties / args / description
      Previous value: -"Action-specific arguments — see the description."New value: +"Arguments for the chosen action; required fields depend on `action`."
    • addedInput schema / properties / args / properties
      Added value: +{
+  "country": {
+    "description": "Party country code (set, optional).",
+    "type": "string"
+  },
+  "gln": {
+    "description": "GS1 Global Location Number for the party (set, optional).",
+    "type": "string"
+  },
+  "id": {
+    "description": "Passport id (required).",
+    "type": "string"
+  },
+  "legacyOperatorId": {
+    "description": "Your internal operator id for the party (set, optional).",
+    "type": "string"
+  },
+  "legalName": {
+    "description": "Party legal name. Required for set.",
+    "type": "string"
+  },
+  "role": {
+    "description": "Economic-operator role, e.g. manufacturer | importer | distributor | authorised_representative (required).",
+    "type": "string"
+  }
+}
    • removedInput schema / properties / args / propertyNames
      Removed value: -{
-  "type": "string"
-}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "error": {
+      "description": "Machine-readable error code, when the API rejected the request.",
+      "type": "string"
+    },
+    "id": {
+      "description": "The resource's TracePass id, when the response is a single entity.",
+      "type": "string"
+    },
+    "items": {
+      "description": "The page of results, when the action is a list.",
+      "items": {},
+      "type": "array"
+    },
+    "limit": {
+      "description": "Page size (list actions).",
+      "type": "number"
+    },
+    "message": {
+      "description": "Human-readable error or status detail, when present.",
+      "type": "string"
+    },
+    "page": {
+      "description": "Current page number (list actions).",
+      "type": "number"
+    },
+    "result": {
+      "description": "Wraps a non-object response body (e.g. a QR code string)."
+    },
+    "total": {
+      "description": "Total matching records across all pages (list actions).",
+      "type": "number"
+    },
+    "totalPages": {
+      "description": "Total number of pages (list actions).",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only provide idempotentHint=true, so the description carries the behavioral burden and does so richly: a gln/operatorIdentifier mismatch returns 400, a scheme-gln operatorIdentifier also fills the top-level gln while facilityIdentifier never does, and typeds are excluded from AI extraction/CSV import. These are non-obvious behaviors beyond anything in the structured fields.

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?

It is long, but the length is earned by real complexity (two actions, six roles, four identifier schemes) and is well front-loaded and sectioned with bullets. The identifier-scheme enumeration is detailed but necessary; only minor tightening is possible.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with nested objects, an action enum, and an output schema already present, the description supplies everything an agent needs to call it correctly (required fields per action, identifier fallbacks, scheme syntaxes, error conditions). Return values need not be explained given the output schema exists.

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 coverage is 100%, so baseline is 3, but the description adds genuine cross-field semantics: the at-least-one-identifier rule (gln/legacyOperatorId/operatorIdentifier), the agreement constraint between gln and operatorIdentifier, and the four operatorIdentifier schemes with their shapes. This goes beyond the per-field schema descriptions.

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?

Opens with a specific verb+resource ("Manage the economic-operator parties on a passport") and enumerates the exact roles covered (manufacturer, importer, authorisedRepresentative, distributor, recycler, producerResponsibilityOrg). This clearly distinguishes it from siblings like tracepass_passport_fields and tracepass_passports, which handle different sub-resources.

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 two actions (set/remove) are documented with their full args, giving clear context for when each applies, and the note that typed identifiers are "not set by AI extraction or CSV import" signals a manual-only usage constraint. It stops short of explicitly routing the agent against sibling tools when a party vs. a generic field is at stake, so it is not a full 5.

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

All TracePass toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources