Skip to main content
Glama

TracePass passport fields

tracepass_passport_fields
DestructiveIdempotent

Update field values on a Digital Product Passport. Every change is audit-logged with the credential (API key or connected app) and this MCP channel.

source (optional): omit it or pass "manual" when the user gave you the value or it comes from their own records — written with the user's rights (approved for an API key or an admin; sent to review for a connected app acting for an editor). Pass "ai_suggested" when you found or inferred it yourself: it goes to the dashboard review queue for a human, and is refused on fields only the operator may state or that must be measured (e.g. stateOfHealth).

Actions (pass via action; {…} is the args object):

  • update — { id, fieldKey, value, source? }. value type matches the field's dataType.

  • update_by_serial — { serial, fieldKey, value, gtin?, source? }. On 409 ambiguous_serial (a serial is unique only WITHIN a GTIN) pass gtin.

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": {
      "action": "<action>"
    },
    "name": "tracepass_passport_fields"
  }
}

Input Schema

NameRequiredDescriptionDefault
argsNo
actionYes

Output Schema

NameRequiredDescriptionDefault
idNo
pageNo
errorNo
itemsNo
limitNo
totalNo
resultNo
messageNo
totalPagesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed17 schema fields changed
    • removedInput schema / properties / action / description
      Removed value: -"Update one passport field, addressed by passport id (update) or by your serial (update_by_serial)."
    • removedInput schema / properties / args / description
      Removed value: -"Arguments for the chosen action; required fields depend on `action`."
    • removedInput schema / properties / args / properties / fieldKey / description
      Removed value: -"The field key to set (required)."
    • removedInput schema / properties / args / properties / gtin / description
      Removed value: -"GTIN disambiguator for update_by_serial when the serial isn't unique (else 409)."
    • removedInput schema / properties / args / properties / id / description
      Removed value: -"Passport id. Required for update."
    • removedInput schema / properties / args / properties / serial / description
      Removed value: -"Your serial. Required for update_by_serial."
    • changedInput schema / properties / args / properties / source / description
      Previous value: -"Where the value came from: \"manual\" (default — the user's statement) or \"ai_suggested\" (you found it; it goes to human review)."New value: +"manual (default) | ai_suggested (goes to human review)."
    • removedInput schema / properties / args / properties / value / description
      Removed value: -"The new value for the field (required). Type depends on the field's dataType."
    • removedOutput schema / properties / error / description
      Removed value: -"Machine-readable error code, when the API rejected the request."
    • removedOutput schema / properties / id / description
      Removed value: -"The resource's TracePass id, when the response is a single entity."
    • removedOutput schema / properties / items / description
      Removed value: -"The page of results, when the action is a list."
    • removedOutput schema / properties / limit / description
      Removed value: -"Page size (list actions)."
    • removedOutput schema / properties / message / description
      Removed value: -"Human-readable error or status detail, when present."
    • removedOutput schema / properties / page / description
      Removed value: -"Current page number (list actions)."
    • removedOutput schema / properties / result / description
      Removed value: -"Wraps a non-object response body (e.g. a QR code string)."
    • removedOutput schema / properties / total / description
      Removed value: -"Total matching records across all pages (list actions)."
    • removedOutput schema / properties / totalPages / description
      Removed value: -"Total number of pages (list actions)."
  2. Changed4 schema fields changed
    • 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"
      +]
  3. Changed4 schema fields changed
    • 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"
  4. Changed1 schema field changed
    • addedInput schema / properties / args / properties / source
      Added value: +{
      +  "description": "Where the value came from: \"manual\" (default — the user's statement) or \"ai_suggested\" (you found it; it goes to human review).",
      +  "enum": [
      +    "manual",
      +    "ai_suggested"
      +  ],
      +  "type": "string"
      +}
  5. Changed6 schema fields changed
    • addedInput schema / properties / action / description
      Added value: +"Update one passport field, addressed by passport id (update) or by your serial (update_by_serial)."
    • 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: +{
      +  "fieldKey": {
      +    "description": "The field key to set (required).",
      +    "type": "string"
      +  },
      +  "gtin": {
      +    "description": "GTIN disambiguator for update_by_serial when the serial isn't unique (else 409).",
      +    "type": "string"
      +  },
      +  "id": {
      +    "description": "Passport id. Required for update.",
      +    "type": "string"
      +  },
      +  "serial": {
      +    "description": "Your serial. Required for update_by_serial.",
      +    "type": "string"
      +  },
      +  "value": {
      +    "description": "The new value for the field (required). Type depends on the field's dataType."
      +  }
      +}
    • 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"
      +}
  6. Changed1 schema field changed
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "update"
      -]New value: +[
      +  "update",
      +  "update_by_serial"
      +]
  7. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that every change is audit-logged with the credential and channel, that write authorization differs by credential type (API key/admin writes, a connected app acting for an editor goes to review), and that ai_suggested values are refused on operator-only or measured fields such as stateOfHealth. These are exactly the side effects and failure modes an agent needs before mutating passport data.

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?

The action list is cleanly front-loaded and each bullet maps to one call shape. The `source` paragraph is dense and awkwardly nested with parentheticals ('approved for an API key or an admin; sent to review for a connected app acting for an editor'), costing readability, but no sentence is filler.

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 destructive mutation tool with an output schema, the description covers what changes are logged, the permission matrix, the review fallback, and one concrete error path. Remaining omissions are minor: nothing about whether field values can be reverted or what happens to prior values, and `id` is undefined.

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 description coverage is 0%, so the description carries the burden, and it largely does: `source` semantics and defaults, the value-type/dataType relationship, the role of `serial` plus `gtin` in disambiguation, and `fieldKey` as the target. The notable gap is `id`, which is never explained (presumably the passport identifier), leaving the agent to infer it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence gives a specific verb and resource ('Update field values on a Digital Product Passport'), which is clearly distinct from the lifecycle, parties, and EPCIS siblings. It does not explicitly name a sibling to differentiate against, but the resource-and-operation framing is unambiguous.

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 explicitly covers when to omit `source`, when to pass "manual" versus "ai_suggested", and what each choice triggers (direct write vs. human review queue). The two actions are laid out with their args, including a specific directive to pass `gtin` on a 409 ambiguous_serial, which is real when-to-use routing. What it lacks is any guidance on when this tool should not be used relative to sibling passport tools.

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.