Skip to main content
Glama

Who is paying me: what the ledger holds about a paying wallet (free)

payer_check
Read-onlyIdempotent

Use this when you sell to agents (an x402 seller, a marketplace, an API) and want to know who is on the other side before you serve or after a payment arrives: give wallet, the 0x address that is paying you. Returns whether a Base ERC-8004 registration is bound to it (any bound wallet), how many, the highest-level one in short (level, last payment, whether its Agent Pass holds and until when, the Watch reading of its newest payment, open incidents, detections in 30 days), what the address itself is in our feed (plain key, contract or EIP-7702 delegate, frozen by an issuer, planted as a poisoning look-alike), and the items worth a look, each with its source. A wallet with no registration is reported as such: that is not a statement about it. Facts, never a verdict; you decide whom to serve.

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": {
      "wallet": "<wallet>"
    },
    "name": "payer_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletYesThe 0x address that is paying you

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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, so safety is covered. The description goes further by enumerating what the response contains (binding count, highest-level agent details, Pass validity, Watch reading, incidents, 30-day detections) and by warning that a missing registration 'is not a statement about it' — a genuinely useful non-obvious caveat. It says nothing about cost or latency beyond the title's 'free', and nothing about invalid-input behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The usage condition is front-loaded, which is good, but the body is one long run-on sentence carrying a deeply nested parenthetical list of return fields. Every clause is informative, yet the packing makes it hard to scan; splitting the return inventory into a short structured sentence would cost nothing in length and gain a lot in readability.

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 explaining returns and does so in detail, including the key negative case (no registration) and the seller decision framing. Given one required parameter and closed-world reads, an agent has enough to call it correctly. Only error/empty-input behavior is left unaddressed.

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 required parameter with 100% schema description coverage, so the schema already does the work. The description's 'the 0x address that is paying you' restates the schema text rather than adding format, checksum, or chain constraints. Baseline 3 applies.

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 states a concrete operation on a concrete resource: given a 0x paying address, it returns whether a Base ERC-8004 registration is bound, plus feed status and flags. The framing ('when you sell to agents... who is on the other side') makes the seller-side use case unmistakable. It does not explicitly name how it differs from nearby siblings such as pay_check or counterparty_preview, so it stops short of a 5.

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?

Timing is stated clearly: call it 'before you serve or after a payment arrives', and the audience is named (x402 seller, marketplace, API). It also sets an interpretive boundary ('Facts, never a verdict; you decide whom to serve'). No explicit when-not conditions or named alternatives are given, which keeps it from a 5.

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.