Skip to main content
Glama

Nine facts about an address before paying it (free)

payee_facts
Read-onlyIdempotent

Use this for the address your agent was given to pay; for the paying agent itself, use pay_check. What the chain and our ledger say about an address an agent is about to pay (payee.facts.v2): its code kind (plain key, contract, EIP-7702 delegated) and whether the delegate matches a known sweeper or the tiny-forwarder shape; whether it forwards most of what it receives within minutes (relay shape); whether its stablecoin outflow goes to swap venues; who funds it and where it exits (7 days of Transfer logs); whether a contract exposes a claim-on-proof selector; an issuer freeze; how many registered agents pay it; and, given the paying agent and the amount, whether it is a never-paid destination at a size the agent never sent and whether it is a look-alike of an address in the agent's own history. Each fact carries value, evidence, method and measurement time; an unavailable channel is said, never guessed. Facts describe an address; they do not judge it.

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": {
      "payee": "<payee>"
    },
    "name": "payee_facts"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentNoOptional: the paying agent (token id, slug or bound wallet), for the two per-agent facts
payeeYesThe 0x address to be paid
amount_usdNoOptional: the amount about to be paid, in USD

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/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 the safety profile is covered. The description adds real behavior beyond that: data sources (chain plus internal ledger, 7 days of Transfer logs), per-fact structure (value, evidence, method, measurement time), and the important guarantee that an unavailable channel is stated rather than inferred. It stops short of stating latency, cost, or caching behavior, hence not a 5.

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 routing guidance is correctly front-loaded, but the body is a single dense run-on sentence that strings nine facts together with semicolons, making it harder to scan than a short list would be. Most content earns its place, yet the formatting works against quick comprehension.

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 must describe returns, and it does so reasonably: each fact carries value, evidence, method and measurement time, and missing channels are reported rather than guessed. It is nearly complete for a read-only fact-gathering tool; only the exact fact names or ordering are left unspecified.

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 baseline is 3, but the description goes further by explaining why the two optional parameters exist: 'given the paying agent and the amount, whether it is a never-paid destination at a size the agent never sent' tells the caller that omitting agent and amount_usd silently drops two of the nine facts. That is meaningful guidance the schema does not convey.

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 names a specific verb and resource ('what the chain and our ledger say about an address an agent is about to pay') and enumerates the nine facts returned, so an agent knows exactly what it gets. It also explicitly distinguishes itself from the sibling pay_check ('for the paying agent itself, use pay_check'), which removes the main ambiguity in a crowded sibling set.

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?

The first clause states the triggering condition (the address your agent was given to pay) and names the alternative tool and the condition selecting it (pay_check for the paying agent). The closing line 'Facts describe an address; they do not judge it' further tells the agent not to expect a verdict here, which is a practical exclusion rule.

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.