Skip to main content
Glama

zato crypto data

Pay-to check: facts about an unknown payTo wallet before an agent pays it (Base or Ethereum)

payto_check
Read-only

Quick facts about a payTo wallet on Base/Ethereum: contract or EOA, nonce, ETH/USDC balance, recent USDC flow, optional domain declaration. Price: $0.001 USDC per call (x402, Base).

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": {
      "address": "<address>"
    },
    "name": "payto_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainNooptional seller domain, e.g. api.example.com: we GET its /.well-known/paycheck.json and /.well-known/x402.json (3 s timeout, public hosts only) and report whether the address is declared there
addressYespayTo address to check (0x + 40 hex chars) or ENS/Basename (vitalik.eth, name.base.eth)
networkNo"base" (default) or "ethereum"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely new behavioral context the annotations cannot convey: a per-call price of $0.001 USDC via x402 on Base, which tells the agent this is a paid, metered call. It stops short of describing failure modes or rate limits.

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 dense sentence that front-loads the resource and scope, then lists the returned facts, with the price appended as a separate clause. No filler or repetition.

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 carries the burden of describing return values and does so by enumerating the five fact categories. The pricing model is disclosed, which is essential for a paid call. It is slightly incomplete in not defining the window for 'recent USDC flow' or what happens on an unresolvable address.

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%, so address, network, and domain are already fully documented in the schema, including the well-known lookup behavior and timeout. The description only echoes 'optional domain declaration' and adds no syntax or format detail beyond the schema, making the baseline 3 appropriate.

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?

Names a specific resource (a payTo wallet) with explicit scope (Base/Ethereum) and enumerates the facts returned: contract vs EOA, nonce, ETH/USDC balance, recent USDC flow, domain declaration. It does not differentiate itself from plausible siblings such as wallet_report or preflight, so an agent must infer the distinction from the name and title alone.

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 'before an agent pays it' framing lives in the title rather than the description, and the description itself only implies usage by calling these 'quick facts' about a payTo wallet. There is no explicit when-to-use, when-not-to-use, or named alternative among the many wallet-related siblings.

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.

Resources