Skip to main content
Glama
malinoto

tracepass-mcp-server

by malinoto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

TracePass products

tracepass_products

List, create, update, archive, and batch-create products in the TracePass catalogue. Products are the catalogue layer for Digital Product Passports, each with one passport per serialised unit.

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, chemicals, 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

TableJSON Schema
NameRequiredDescriptionDefault
argsNoArguments for the chosen action; required fields depend on `action` (see each action above).
actionYesWhich product operation to run: list | get | create | create_batch | update | archive.

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. Changed7 schema fields changedv1.7.3
    • 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"
+}
  2. First observedv1.1.4

TDQS

A4.7/5.0
Behavior5/5

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

Despite minimal annotations (only idempotentHint=false), the description discloses important behaviors: list/get are read-only, create_batch has partial success with per-item status and consumes N writes upfront with 429 on daily cap, and archive is soft, reversible, and blocked with 409 when referenced by non-archived passports. This exceeds typical transparency expectations.

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?

The description is well-structured with a clear opening, a contextual paragraph, and bulleted actions. Each sentence adds value—no fluff. The format is scannable and information-dense without being verbose, earning a high score.

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?

The tool is complex with six actions and nested args, but the description covers every action's arguments, constraints, error conditions, and edge cases (partial success, rate limit, conflict). Presence of an output schema means return-value details are not needed. Sibling context and annotations are adequately supplemented.

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 adds meaningful semantics beyond the schema: category enum values, update requiring at least one field, batch element structure, and list filters. It also clarifies constraints like limit ≤100 and page numbering, which the schema describes but the description reinforces for usability.

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 opens with 'Manage the TracePass product catalogue' and clearly defines the product as the catalogue layer, distinguishing it from passports and other sibling tools. It enumerates six specific actions with their arguments, making the tool's purpose and scope unmistakable.

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 description gives clear context on when to use this tool ('Manage the TracePass product catalogue') and explains the relationship to passports, implying use for catalogue-level operations. It does not explicitly name alternative tools for exclusion, but the product/passport distinction provides sufficient guidance.

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

Deploy Server

Other Tools