Skip to main content
Glama

zato crypto data

Historical balance: ETH and USDC of an address at a past date or block (Ethereum, Base, Optimism)

balance_at
Read-only

ETH and USDC balance of an address at a past date or block (Ethereum, Base, Optimism). Price: $0.003 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": "balance_at"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoISO date/time (UTC), e.g. 2025-01-01
blockNoor a block number instead of date
addressYesaddress or ENS/Basename
networkNoethereum (default), base or optimism

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/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 does add genuinely useful behavioral context the annotations lack: a per-call price of $0.003 USDC paid via x402 on Base. However, it does not disclose what happens when neither date nor block is supplied, whether the two are mutually exclusive, or how multi-chain/token results are returned.

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?

Two short sentences with the capability front-loaded and the cost appended, so nothing is buried. The first sentence nearly restates the title verbatim, which is mild redundancy, but there is no padding or wasted prose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only lookup with no output schema and fully documented parameters, the description is workable but leaves meaningful gaps: no statement of default behavior with only an address, no clarification of date-vs-block precedence, and no note on how ENS/Basename resolution behaves on Base or Optimism. Adequate, not complete.

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 each parameter (date, block, address, network) is already documented with examples and defaults, establishing the baseline of 3. The description only reinforces the network options and confirms that only ETH and USDC are covered, which slightly narrows expectations but adds little syntax or constraint detail 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?

The description names a concrete resource and scope: ETH and USDC balances of an address at a past date or block across Ethereum, Base, and Optimism. The verb is implicit (retrieval) but the historical framing plus the explicit token and chain scope make it distinguishable from a current-balance tool like usdc_balance, even though no sibling is named.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no pointer to an alternative for current (non-historical) balances or for other tokens. An agent must infer from the words 'past date or block' that this is the historical counterpart to a live balance lookup.

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