Skip to main content
Glama

zato crypto data

Counterparty report: pay-to facts + wallet age + presence on 12 EVM chains in one call

counterparty_report
Read-only

Before paying or trusting an unknown address: pay-to facts + wallet age + presence on 12 chains in one answer. Price: $0.005 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": "counterparty_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainNooptional seller domain to check the payTo declaration
addressYesaddress or ENS/Basename
networkNo"base" (default) or "ethereum" for the pay-to facts

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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 non-obvious behavior: the $0.005 USDC cost, the x402 payment protocol on Base, and that all three fact sets come back in one answer rather than requiring multiple calls. It does not cover latency, error behavior for malformed addresses, 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?

Two short sentences, with the use case front-loaded ahead of the composite output list and the price last. Nothing is wasted or repeated.

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 returns and does so by enumerating the three fact categories. Cost and payment mechanism are disclosed. Minor gaps remain around the optional domain parameter's effect on results and failure modes.

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 coverage is 100%, so address, domain, and network are already fully documented in the schema. The description reinforces what the call produces (pay-to facts, wallet age, chain presence) but adds no syntax or format detail beyond the schema, so the 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 names a specific verb-phrase and composite resource: pay-to facts, wallet age, and presence on 12 chains for an unknown address. It is clearly distinguishable from narrower siblings like wallet_age or payto_check because it bundles all three. It stops short of explicitly naming which sibling to use instead, so it lands at 4 rather than 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?

"Before paying or trusting an unknown address" gives a concrete trigger condition that an agent can act on. There are no exclusions or named alternatives (e.g., preflight, wallet_report, multichain_wallet_report), which leaves overlap with siblings unresolved.

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