Skip to main content
Glama

Pre-payment counterparty check

check_payment_counterparty
Read-only

Check a wallet/payTo address before paying it: sanctioned crypto address (OFAC/UK/EU), x402 seller reputation, live Base facts, optional counterparty-name screening, signed receipt. Verdict block/review/clear. $0.005 per call after the free daily quota.

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": "check_payment_counterparty"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoOptional counterparty person or company name to sanctions-screen
chainNoChain for live on-chain facts (default base). The sanctions check covers every chain.
addressYesWallet / payTo address (EVM 0x..., BTC, TRX, ...)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered; the description adds real context beyond that: the three-valued verdict (block/review/clear), the existence of a signed receipt, the fact that sanctions coverage spans all chains, and the pricing model ($0.005 per call after a free daily quota). It does not disclose latency, quota size, or what the receipt attests to, which keeps it short of 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.

Conciseness4/5

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

The definition is dense but front-loaded: the purpose and check list come first, then the verdict vocabulary, then pricing. Every clause carries information, with only minor redundancy between the 'sanctioned crypto address' wording and the chain-coverage note.

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 three parameters, full schema coverage, and annotations already carrying the read-only posture, the description supplies what is missing: the verdict vocabulary stands in for an absent output schema and pricing sets cost expectations. What remains unstated is the shape of the returned facts beyond the verdict label and the receipt's issuer, which is a modest gap for a paid, open-world lookup.

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 all three parameters (address, chain with its enum, optional name) are already documented, which sets the baseline at 3. The description reinforces that the name parameter is optional screening and that the chain parameter governs live facts while sanctions cover every chain, but this largely restates the schema rather than adding new syntax or format guidance.

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 names a specific verb and resource ('Check a wallet/payTo address before paying it') and enumerates exactly what is checked: sanctions lists (OFAC/UK/EU), x402 seller reputation, live Base facts, optional name screening, signed receipt. That is far more specific than the title alone, though it never contrasts itself with the siblings check_token or verify_receipt, leaving the agent to infer the boundary between 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?

'before paying it' gives a clear trigger condition, and the phrase 'optional counterparty-name screening' signals that name screening is discretionary rather than mandatory. There is no explicit when-not-to-use statement and no named alternative tool, so the agent must infer that token checks belong to check_token and receipt checks to verify_receipt.

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