Skip to main content
Glama

zato crypto data

Multichain wallet report: one address on 12 EVM chains (Ethereum, Base, Arbitrum, Optimism, Polygon, BNB, Avalanche ...) in one call

multichain_wallet_report
Read-only

One wallet across all 12 EVM chains at once (or a chains= subset): where does it hold funds and where is it active. Price: $0.008 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": "multichain_wallet_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainsNooptional comma-separated subset, e.g. ethereum,base,bnb (default: all 12 chains)
addressYeswallet or contract address (0x + 40 hex chars) or ENS/Basename (vitalik.eth, name.base.eth)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, yet the description adds a genuinely non-obvious trait: the call is paid at $0.008 USDC via x402 on Base. That is important operational context an agent cannot get from structured fields. It stops short of describing response shape or latency beyond the one-line holdings/activity summary.

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, front-loaded with the core capability and followed by the pricing caveat. No padding, no restatement of the tool name, and the parenthetical subset option sits right next to the scope statement.

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?

For a two-parameter read-only tool with no output schema, the description covers scope, chain coverage, cost, and a rough sense of the returned information (holdings and activity). A little more on what a caller receives per chain would make it complete, but nothing essential is missing.

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 both the address format (0x/ENS/Basename) and the comma-separated chains subset are fully documented in the schema. The description only echoes the chains= subset and the single-wallet nature, adding marginal meaning beyond the schema.

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?

States a concrete verb-and-resource combination: aggregate holdings and activity for one wallet across 12 EVM chains, with an optional per-chain subset. The 'one wallet' phrasing implicitly contrasts with the batch sibling, but it never names wallet_report or batch_wallet_report, so differentiation relies on inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Use context is implied by 'all 12 EVM chains at once (or a chains= subset)', which tells the agent this is the multi-chain sweep option. There is no explicit when-not guidance or named alternative for single-chain lookups, so routing is left partly to the agent.

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