Skip to main content
Glama

verify

Destructive

x402 paid seal-registry verification; use only after separate payment authorization, not for free lookup. Arguments that cannot be a seal UUID are HTTP 400 before payment. Empty arguments are unpaid HTTP 402. Paid calls are answered from the seal registry at $0.05 USDC on Base. For free verification use verify_record.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
tierNoSignal tier. ping: registry existence only. verify (default): signature and validity baseline. evidence: the baseline plus a SHA-256 digest of the returned answer. The HTTP 402 quote states the exact price. No tier claims real-world authenticity.
sealIdNoRequired seal UUID. productId and serial are not registry keys.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / tier
      Added value: +{
      +  "description": "Signal tier. ping: registry existence only. verify (default): signature and validity baseline. evidence: the baseline plus a SHA-256 digest of the returned answer. The HTTP 402 quote states the exact price. No tier claims real-world authenticity.",
      +  "enum": [
      +    "ping",
      +    "verify",
      +    "evidence"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the payment protocol: malformed seal IDs yield HTTP 400 before any charge, empty arguments yield an unpaid 402, and successful calls cost $0.05 USDC on Base read from the seal registry. That the call spends money is exactly the context an agent needs given destructiveHint=true and readOnlyHint=false. It stops short of stating whether repeated paid calls are re-charged, which matters because idempotentHint is false.

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?

Five tight sentences, each carrying a distinct fact: purpose, payment precondition, two error contracts, price/source, and the free alternative. The payment gate is front-loaded and there is no redundant restatement of the schema.

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?

With no output schema, the description is expected to carry return-value context, and it partially does by naming the registry as the answer source and by letting the tier documentation describe the digest payload. The remaining gap is what a successful paid response looks like structurally and whether repeat calls incur repeat charges.

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 the tier enum and sealId format are already documented. The description still adds real value by clarifying that anything which cannot be parsed as a seal UUID fails at HTTP 400 before payment and that empty arguments are unpaid 402 — which resolves the ambiguity of a schema with no fields marked required.

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?

States a specific verb and resource ('paid seal-registry verification') and immediately scopes it as the x402 payment-gated variant. It explicitly names the sibling it is not ('For free verification use verify_record'), so an agent can separate it from verify_record without opening either schema.

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

Usage Guidelines5/5

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

Gives both the precondition ('use only after separate payment authorization') and the exclusion ('not for free lookup'), plus the concrete alternative to route to. Nothing about when to choose this tool over verify_record is left to inference.

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.