TracePass

TracePass EPCIS 2.0

tracepass_epcis

GS1 EPCIS 2.0 supply-chain events. export, capture, capture_job and query are on every plan, Free included. Captured events count against the plan's event allowance (10 a month on Free); over it, capture returns an overage or hard-block message.

Actions (pass via action, with args):

export — args: { id }. Export a passport's events as an EPCIS 2.0 JSON-LD document. Read-only.
export_by_serial — args: { serial, gtin? }. Same as export, addressed by your own serial. A serial is unique only WITHIN a GTIN — if it isn't unique in your account the call returns 409 ambiguous_serial; pass gtin (or use export by id). Read-only.
capture — args: { events }. events is an EPCISDocument, a single event, or an array of events (JSON-LD). Returns a 202 with a captureJobId.
capture_job — args: { jobId }. Poll an async capture job. Read-only.
query — args: { params? }. params is a key/value map of standard EPCIS query parameters (EQ_bizStep, GE_eventTime, MATCH_epc, …). Read-only.

Input Schema

Name	Required	Description	Default
`args`	No	Arguments for the chosen action; required fields depend on `action`.
`action`	Yes	EPCIS 2.0: export a passport's events (export \| export_by_serial), capture new events, poll a capture job, or query events.

Output Schema

Name	Required	Description
`id`	No	The resource's TracePass id, when the response is a single entity.
`page`	No	Current page number (list actions).
`error`	No	Machine-readable error code, when the API rejected the request.
`items`	No	The page of results, when the action is a list.
`limit`	No	Page size (list actions).
`total`	No	Total matching records across all pages (list actions).
`result`	No	Wraps a non-object response body (e.g. a QR code string).
`message`	No	Human-readable error or status detail, when present.
`totalPages`	No	Total number of pages (list actions).

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 11, 2026
- addedOutput schema / properties / error / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / error / type
```
Removed value: -"string"
```
- addedOutput schema / properties / message / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / message / type
```
Removed value: -"string"
```

Changed6 schema fields changedJun 14, 2026

addedInput schema / properties / action / description

Added value: +"EPCIS 2.0: export a passport's events (export | export_by_serial), capture new events, poll a capture job, or query events."

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: +{
+  "events": {
+    "description": "EPCIS 2.0 event payload (an EPCISDocument or event list). Required for capture."
+  },
+  "gtin": {
+    "description": "GTIN disambiguator for export_by_serial when the serial isn't unique (else 409).",
+    "type": "string"
+  },
+  "id": {
+    "description": "Passport id. Required for export.",
+    "type": "string"
+  },
+  "jobId": {
+    "description": "Capture job id to poll. Required for capture_job.",
+    "type": "string"
+  },
+  "params": {
+    "additionalProperties": {
+      "type": "string"
+    },
+    "description": "EPCIS query parameters as key→value strings (query, optional).",
+    "propertyNames": {
+      "type": "string"
+    },
+    "type": "object"
+  },
+  "serial": {
+    "description": "Your serial. Required for export_by_serial.",
+    "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"
+}

Changed1 schema field changedJun 14, 2026

changedInput schema / properties / action / enum

Previous value: -[
-  "export",
-  "capture",
-  "capture_job",
-  "query"
-]New value: +[
+  "export",
+  "export_by_serial",
+  "capture",
+  "capture_job",
+  "query"
+]

First observedJun 9, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations are sparse (tool-level readOnlyHint=false, destructiveHint=false), so the description carries the burden and delivers: per-action read-only flags, the plan/quota model (10 events/month on Free, plan event allowance), the overage/hard-block message on capture, the async 202 + captureJobId + capture_job polling pattern, and the 409 ambiguous_serial condition. The per-action read-only notes clarify rather than contradict the conservative tool-level readOnlyHint=false, since capture writes.

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?

Front-loaded with what the tool is, then the plan/allowance caveat, then a tight bulleted action list. Every sentence earns its place—no repetition of schema content beyond the necessary arg mapping.

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?

With an output schema present, return values need not be explained, and the description still covers the async capture lifecycle, quota/overage behavior, ambiguity error handling, and per-action read-only status. Nothing an agent needs to invoke it correctly is missing.

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 the baseline is 3, but the description adds real value by mapping each arg to its action (id→export, serial/gtin→export_by_serial, events→capture, jobId→capture_job, params→query) and by naming example query keys (EQ_bizStep, GE_eventTime, MATCH_epc) that the schema leaves generic.

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 identifies the resource (GS1 EPCIS 2.0 supply-chain events) and enumerates five distinct actions with a one-line purpose for each, including the subtle export vs export_by_serial distinction. An agent can distinguish this event-oriented tool from the sibling product/passport/template tools 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?

It gives clear per-action selection guidance, notably the export vs export_by_serial decision rule (serial is unique only within a GTIN; pass gtin or use id to avoid 409). It does not, however, state when to reach for this tool over the sibling tools. No explicit exclusions.

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

All TracePass tools Inspect

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.