Skip to main content
Glama

A2A Passport — one GTIN, one call, everything GSC knows, signed

Get Passport

get_passport
Idempotent

The signed passport of a product (a Global Trade Item Number, GTIN) or a retail banner (market/banner, e.g. FR/Carrefour): which hub holds its record, where it is on the record, its compliance records, who lists it, where the payment door is. Read live from the wefetch hubs on every call; the first call issues version 1. subject = a GTIN (8 to 14 digits) or market/banner; kind = gtin or banner (optional).

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": {
      "subject": "<subject>"
    },
    "name": "get_passport"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
subjectYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedOutput schema / additionalProperties
      Removed value: -true
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

The annotations declare readOnlyHint=false with idempotentHint=true, and the description explains why: it reads live from the wefetch hubs on every call but 'the first call issues version 1', i.e. it materializes a versioned record. That is genuine behavioral context an agent could not derive from the annotations alone, and it is consistent with openWorldHint=true. It does not mention auth requirements or failure modes, so it stops short of a 5.

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 resource is front-loaded and the parameter definitions are packed into a single trailing clause with no filler. It is dense and jargon-heavy ('where the payment door is', 'where it is on the record'), which costs some immediate readability, but every clause carries information.

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?

An output schema exists, so return values need not be described, and the description still covers the two inputs plus the versioning side effect of the first call. What remains missing is routing guidance against the two sibling tools, the one piece an agent needs for this open-world, version-creating fetch.

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 full burden and does so: 'subject' is defined as a GTIN of 8 to 14 digits or a market/banner like FR/Carrefour, and 'kind' is defined as gtin or banner and marked optional. The only gap is that it never states what happens when 'kind' is omitted or how it is inferred from 'subject'.

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 description names a concrete resource — 'the signed passport of a product (GTIN) or a retail banner' — and enumerates what it contains (hub, record location, compliance records, listings, payment door), so an agent knows exactly what it retrieves. It does not explicitly differentiate itself from the sibling verify_passport or list_passports, which keeps it short of a 5.

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

Usage Guidelines2/5

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

There is no statement of when to call this versus verify_passport or list_passports, and no prerequisites or exclusions. An agent must infer from the tool names alone whether it should fetch a passport or verify/list one, which is exactly the kind of routing decision the description should make.

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.