tracepass-mcp-server

TracePass products

tracepass_products

Destructive

Manage a TracePass product catalogue: list, retrieve, create, batch-create, update, and archive products that group serialised passports by model and category.

Instructions

Manage the TracePass product catalogue. A product is the catalogue layer — one product can have many passports (one per serialised unit). Products are not billable on their own.

Actions (pass via action, with args):

list — args: { page?, limit? (≤100), category?, status?, search? }. Read-only.
get — args: { id }. Read-only.
create — args: { name, model, category, description? }. category is one of: battery, textile, electronics, construction, steel, detergents, paints-coatings, packaging, furniture, tyres, jewelry, toys, fmcg.
update — args: { id, name?, model?, description? }; pass at least one field to change.
create_batch — args: { products: [ { name, model, category, description? }, … ] }, up to 100. Partial-success: the response carries a per-item status, so some items can be created while others error. The whole batch consumes N writes upfront; if that would exceed the daily cap NOTHING is created (429).
archive — args: { id }. Soft-archive a product. Blocked with 409 while any non-archived passport still references it — archive those passports first. This is reversible and is NOT deletion.

Input Schema

Name	Required	Description	Default
`args`	No	Arguments for the chosen action; required fields depend on `action` (see each action above).
`action`	Yes	Which product operation to run: list \| get \| create \| create_batch \| update \| archive.

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 changedv1.23.2Oct 31, 2026

removedOutput schema / properties / error / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / error / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / message / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / message / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Changed4 schema fields changedv1.19.1Oct 14, 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"
```

Changed1 schema field changedv1.8.0Sep 28, 2026

changedInput schema / properties / args / properties / category / description

Previous value: -"DPP category for create: battery | textile | electronics | construction | steel | chemicals | packaging | furniture | tyres | jewelry | toys | fmcg."New value: +"DPP category for create: battery | textile | electronics | construction | steel | detergents | paints-coatings | packaging | furniture | tyres | jewelry | toys | fmcg."

Changed7 schema fields changedv1.7.3Aug 7, 2026

addedInput schema / properties / action / description

Added value: +"Which product operation to run: list | get | create | create_batch | update | archive."

changedInput schema / properties / action / enum

Previous value: -[
-  "list",
-  "get",
-  "create",
-  "update"
-]New value: +[
+  "list",
+  "get",
+  "create",
+  "create_batch",
+  "update",
+  "archive"
+]

removedInput schema / properties / args / additionalProperties
```
Removed value: -{}
```

changedInput schema / properties / args / description

Previous value: -"Action-specific arguments — see the description for each action's shape."New value: +"Arguments for the chosen action; required fields depend on `action` (see each action above)."

addedInput schema / properties / args / properties

Added value: +{
+  "category": {
+    "description": "DPP category for create: battery | textile | electronics | construction | steel | chemicals | packaging | furniture | tyres | jewelry | toys | fmcg.",
+    "type": "string"
+  },
+  "description": {
+    "description": "Free-text product description (create/update).",
+    "type": "string"
+  },
+  "id": {
+    "description": "Product id. Required for get and update.",
+    "type": "string"
+  },
+  "limit": {
+    "description": "Page size for list, max 100.",
+    "type": "number"
+  },
+  "model": {
+    "description": "Manufacturer model / SKU. Required for create; optional on update.",
+    "type": "string"
+  },
+  "name": {
+    "description": "Product name. Required for create; optional on update.",
+    "type": "string"
+  },
+  "page": {
+    "description": "Page number for list (1-based).",
+    "type": "number"
+  },
+  "products": {
+    "description": "Products to create for create_batch: [{ name, model, category, description? }], max 100.",
+    "items": {
+      "additionalProperties": {},
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "search": {
+    "description": "Filter list by a search term.",
+    "type": "string"
+  },
+  "status": {
+    "description": "Filter list by product status.",
+    "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"
+}

First observedv1.1.4Jun 9, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Goes well beyond the annotations: create_batch partial-success semantics, per-item statuses, the N-writes-upfront reservation rule and the 429 fail-closed behavior, the 409 guard, and explicit reversibility ('This is reversible and is NOT deletion') for archive. These are exactly the operational traits an agent cannot infer from the schema.

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 the domain model, then a scannable per-action bullet list. Every line carries a constraint, enum, or failure mode; there is no filler prose despite the density.

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?

An output schema exists so return values need no explanation, yet the description still flags the one output detail that matters operationally (per-item status in batch responses). Combined with the write-cap, conflict, and reversibility notes, nothing an agent needs 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 baseline is 3. The description still adds action-scoped meaning the schema cannot express, such as which fields are required per action and 'pass at least one field to change' for update, though the category enum and limit≤100 are restatements of 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?

States the resource (TracePass product catalogue) and defines it precisely against the adjacent concept: 'one product can have many passports (one per serialised unit)'. That single clause removes the ambiguity with the sibling tracepass_passports tool, and the action list spells out the verb set.

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

Usage Guidelines5/5

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

Each action carries its own argument contract and preconditions: archive is blocked with 409 while a non-archived passport references the product, with an explicit instruction to archive passports first. It also states the products/limit cap and that products are not billable, so the agent knows when this tool is not the right lever.

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

Deploy Server