Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Payout wallet check: has an x402 seller's payout wallet changed?

x402_payout_check
Read-only

Check whether an x402 seller's payout wallet changed before you pay it: compares the wallet its live 402 quote names with the wallet its Coinbase Bazaar listing last settled to and with the seller's own /.well-known/paycheck.json. An undeclared change is how a hijacked endpoint looks; a declared rotation passes. Pass or review with reasons, plus the listing's 30-day payers. Never pays or signs. Use before paying a seller you bought from before. Example: url=https://agent-data-tools.revmesh2074.workers.dev/weather. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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": {
      "url": "<url>"
    },
    "name": "x402_payout_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesAbsolute public https URL of the paid x402 endpoint

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Well beyond the annotations (readOnly/non-destructive), it discloses the decision rule — an undeclared change is treated as a hijacked endpoint while a declared rotation passes — the response shape (pass or review with reasons, plus 30-day payers), the side-effect boundary ('Never pays or signs', 'Reads or computes only and changes nothing'), and the billing behavior (each call charged, repeats not free).

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 core check, the decision rule, and the usage trigger are front-loaded in the first three sentences. The trailing pricing/credits sentence ('$0.01/call via x402 USDC or a card key, first 25 free; failed calls free') is relevant cost context but slightly bloats an otherwise tight definition.

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

Completeness5/5

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

For a one-parameter, no-output-schema tool, everything an agent needs is present: what is compared, what verdict comes back and with what supporting data, that it is read-only and never signs, and that calls are billed. Nothing material is left to inference.

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?

There is a single parameter at 100% schema description coverage; the schema already defines 'url' as an absolute public https URL. The description adds a concrete example URL that grounds what a valid target looks like, but no further semantics (host resolution rules, error cases for unreachable origins).

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?

The description states a specific verb and resource — checking whether an x402 seller's payout wallet changed — and immediately specifies the comparison it performs: the live 402 quote's wallet vs. the Coinbase Bazaar listing's last-settled wallet vs. the seller's own /.well-known/paycheck.json. That level of specificity distinguishes it from the many sibling wallet/x402 checks without the agent needing to open any schema.

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?

It gives a clear trigger condition: 'Use before paying a seller you bought from before', and the framing 'before you pay it' scopes it to pre-payment due diligence. It does not explicitly name which sibling to use instead for first-time sellers or general seller vetting (check_x402_seller, x402_check), so the when-not guidance is implied rather than stated.

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.