Skip to main content
Glama

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

Verify Passport

verify_passport
Read-onlyIdempotent

Check a passport: is the signature valid, is the chain of versions intact, how old is the stamp, was any section not read. Verifies from the published key at /.well-known/jwks.json.

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": {
      "passport_id": "<passport_id>"
    },
    "name": "verify_passport"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionNo
passport_idYes

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.5/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior, so the description appropriately focuses on verification semantics. It adds meaningful context by naming the specific checks performed and the source of trust: the published key at /.well-known/jwks.json. It does not explain failure modes or what an invalid result means, but the output schema likely covers return structure.

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 two tight sentences with no wasted wording. It front-loads the verification checks and follows with the key source, which is the most useful additional context. The structure is appropriate for a short tool description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The output schema exists, so the description need not explain return values, and annotations cover safety behavior. However, with 0% schema description coverage, the complete lack of parameter semantics for passport_id and version is a real gap. Usage guidance relative to siblings is also missing, making the definition adequate but incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must explain the two parameters, but it does not. It refers to 'a passport' and 'versions' obliquely, leaving passport_id and especially the optional version parameter undocumented in both schema and prose. An agent cannot tell from the description what version selection does or what format passport_id should take.

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 gives a specific verb-resource pair ('Check a passport' / 'Verifies') and enumerates the checks: signature validity, version-chain integrity, stamp age, and unread sections. This makes the purpose clear without opening the schema. It does not explicitly differentiate itself from siblings such as get_passport or list_passports, so it stops 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 Guidelines3/5

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

The description implies this tool is for verification rather than retrieval, but it never states when to use it instead of get_passport or list_passports. There are no exclusions or prerequisites beyond the implied verification context. This is adequate implied guidance but not explicit routing.

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.