Skip to main content
Glama

Counterparty XDR-1 Passport Verifier (Free)

counterparty_passport_verify
Read-onlyIdempotent

Free bilateral verifier checking a counterparty's XDR-1 receipt signature, published signer, live-registry SKU tier, and timestamp age, returning a signed receipt.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "receipt": {
        "v": "XDR-1",
        "ts": 1762819200,
        "tier": "paid",
        "tool": "counterparty-live-dossier",
        "nonce": "0x2222222222222222222222222222222222222222222222222222222222222222",
        "payer": "0x1111111111111111111111111111111111111111",
        "amount": "500000",
        "signer": "0xa036e2e3e19c6d02f30b3a9eb0acd057e6d9a5c8",
        "recipient": "0xc59c85e661d34084a7769f955d17fd38254a6235",
        "signature": "0x3333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333",
        "input_hash": "0x0000000000000000000000000000000000000000000000000000000000000000",
        "output_hash": "0x0000000000000000000000000000000000000000000000000000000000000000",
        "tool_version": "1.0.0"
      },
      "max_age_seconds": 86400
    },
    "name": "counterparty_passport_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
receiptYesSigned XDR-1 receipt object presented by a counterparty
max_age_secondsNoMaximum acceptable receipt age in seconds (default 86400)

Output Schema

NameRequiredDescriptionDefault
freshNo
validNo
renewal_actionNo
signature_validNo
signer_publishedNo
is_live_registry_attestationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the description needs no safety disclaimers. It adds the verification scope and the fact that a signed receipt is returned, but stays silent on what a failed verification yields and on the trust root behind the 'live-registry SKU tier' check, which is non-obvious jargon.

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?

One dense sentence, front-loaded with the free/bilateral qualifier and the verification dimensions. There is no filler, though the packed list of four checks plus the return clause makes it slightly hard to scan.

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?

With an output schema, full parameter coverage, and annotations in place, the description covers the essential 'what is verified and what comes back'. It falls short on failure outcomes and on the discovery or trust requirements implied by the live-registry tier check, which matter for a verification tool handling nested signed payloads.

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

Parameters3/5

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

Schema description coverage is 100% with only two parameters, so the schema already supplies the semantics. The description's mention of 'timestamp age' loosely corroborates the role of max_age_seconds but adds no format, unit, or behavior detail beyond it, and says nothing about the nested receipt object's many fields.

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 (verifying) and a specific resource (a counterparty's XDR-1 receipt), then enumerates what is checked: signature, published signer, live-registry SKU tier, and timestamp age. It does not explicitly differentiate itself from the sibling receipt_verify, leaving the agent to infer the distinction from the word 'bilateral' and the 'XDR-1' schema.

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?

'Bilateral verifier checking a counterparty's receipt' implies the usage scenario: you hold a receipt someone else issued and want to validate it. However, there is no explicit when-to-use versus when-not, no mention of prerequisites, and no routing to the alternative receipt_verify sibling.

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.