Skip to main content
Glama

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

Payee check: is this payee a verified business before you pay?

payee_check
Read-only

Check a payee before paying it, by domain, paid endpoint URL or payout wallet: its verified record (company in official registers, EU VIES and LEI, OFAC, EU, UN and UK sanctions, wallets proven by signature), the wallet in a live quote compared with the proven ones, and pass, partial, review, unknown or block with reasons and a signed attestation. Never pays or signs. Use before the first payment to a seller. Example: domain=agent-data-tools.revmesh2074.workers.dev. 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

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "payee_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoOr: a paid endpoint; its domain's record is read and its quote's wallet compared
domainNoThe payee's domain, e.g. shop.example.com (give domain, url or address)
addressNoOr: a payout wallet (0x); finds the domain that proved it by signature

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the cost model ($0.01/call, first 25 free, failed calls free), clarifies why repeats are not free (consistent with idempotentHint=false), and states 'Never pays or signs' and 'Reads or computes only and changes nothing' — reinforcing readOnlyHint with concrete guarantees. It also explains what a verdict contains (pass/partial/review/unknown/block with reasons and a signed attestation).

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 purpose and the alternative-input model are front-loaded, and each clause carries information (verdict vocabulary, fees, no-payment guarantee). It is dense and somewhat run-on — the pricing and example sentences could be trimmed — but nothing is purely redundant.

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?

With no output schema, the description takes on the burden of describing returns, and it does: verified-record contents, the wallet-vs-live-quote comparison, the five-level verdict with reasons, and a signed attestation. Combined with the pricing and safety disclosures, an agent has everything needed to invoke it and interpret results.

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 already 100%, so the baseline is 3, but the description adds real meaning: it explains that the three parameters are alternative entry points, that a paid endpoint URL resolves its domain's record and compares its quote wallet, and that an address reverse-maps to the domain that proved it by signature. A concrete domain example is also supplied.

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 ('Check a payee before paying it') and enumerates the three input shapes (domain, paid endpoint URL, payout wallet) plus the record types consulted (official registers, VIES, LEI, OFAC/EU/UN/UK sanctions, signature-proven wallets). This makes it clearly distinct from narrower siblings like sanctions_check, ofac_check, or domain_report without naming them.

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 an explicit usage rule: 'Use before the first payment to a seller,' and the 'before the first payment' framing implicitly scopes it against repeat checks. It does not explicitly name a sibling alternative or a when-not-to-use case, which keeps it short of 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.