Stablecoin Gateways

Verify a receipt (free)

verify_receipt

Read-onlyIdempotent

Free. Verifies an Ed25519 receipt returned by any paid tool: signature, presence in the hash-chained log, and an explorer link for the payment.

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": {
      "receipt": "<receipt>"
    },
    "name": "verify_receipt"
  }
}

Input Schema

Name	Required	Description	Default
`receipt`	Yes	The receipt object from a paid result

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, lowering the burden. The description adds meaningful value beyond that: it is free, it performs signature and hash-chain verification, and it returns an explorer link for the payment.

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?

A single sentence, front-loaded with the cost signal and immediately followed by the verification scope. Every clause earns its place with no redundancy.

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 usefully names what the verification returns (signature status, log presence, explorer link), which is exactly what an agent needs. It does not detail the receipt object's internal fields, a minor gap given the schema documents the parameter.

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% and the single nested 'receipt' object is already documented as coming from a paid result. The description adds no syntax, format, or structure detail beyond what the schema provides, so baseline 3 applies.

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 (verifies) and resource (Ed25519 receipt from any paid tool), then enumerates exactly what is checked: signature, log-chain presence, and explorer link. Siblings are unrelated utilities, so distinguishing this tool is immediate.

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?

'returned by any paid tool' establishes the context in which this tool applies, and 'Free.' signals it is not a metered call. No explicit when-not or alternative is given, but no sibling competes for this role, so a 4 is appropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Stablecoin Gateways tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?