Skip to main content
Glama
cryptoapis-address-latest

cryptoapis-address-latest

Official

EVM address balance and latest activity

evm_address_latest
Read-onlyIdempotent

Query recent EVM address data for balances, nonces, transactions, token transfers, and internal transactions across supported chains without syncing the address.

Instructions

Query latest EVM address data (last 14 days). Cursor pagination: use 'nextStartingAfter' from response as 'startingAfter'.

Actions & supported blockchains: • get-balance: ethereum, ethereum-classic, binance-smart-chain, tron, polygon, avalanche (C-Chain), arbitrum, base, optimism • get-next-nonce: ethereum, ethereum-classic, binance-smart-chain (mainnet, mordor, testnet, sepolia) • list-transactions: ethereum, ethereum-classic, binance-smart-chain, arbitrum, polygon, avalanche (C-Chain), base, optimism, tron • list-token-transfers: ethereum, ethereum-classic, binance-smart-chain, tron, polygon, avalanche (C-Chain), arbitrum, base, optimism • list-internal-transactions: ethereum, ethereum-classic, binance-smart-chain, polygon, avalanche (C-Chain), arbitrum, base, optimism, tron

Blockchain → Networks: • ethereum: mainnet, sepolia • ethereum-classic: mainnet, mordor • binance-smart-chain: mainnet, testnet • polygon: mainnet, amoy • tron: mainnet, nile • avalanche (C-Chain): mainnet, fuji • arbitrum: mainnet, sepolia • base: mainnet, sepolia • optimism: mainnet, sepolia

Credits by action (source: OpenAPI): • get-balance: arbitrum 48, avalanche 54, base 36, binance-smart-chain 75, ethereum 30, ethereum-classic 39, optimism 42, polygon 60, tron 45 • get-next-nonce: arbitrum 32, avalanche 36, base 24, binance-smart-chain 50, ethereum 20, ethereum-classic 26, optimism 28, polygon 40, tron 30 • list-internal-transactions: arbitrum 512, avalanche 576, base 384, binance-smart-chain 800, ethereum 320, ethereum-classic 416, optimism 448, polygon 640, tron 480 • list-token-transfers: arbitrum 352, avalanche 396, base 264, binance-smart-chain 550, ethereum 220, ethereum-classic 286, optimism 308, polygon 440, tron 330 • list-transactions: arbitrum 192, avalanche 216, base 144, binance-smart-chain 300, ethereum 120, ethereum-classic 156, optimism 168, polygon 240, tron 180

Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers.

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": {
      "action": "<action>",
      "blockchain": "<blockchain>",
      "network": "<network>",
      "address": "<address>"
    },
    "name": "evm_address_latest"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of items to return (max 50)
actionYesAction to perform
addressYesAddress to query
contextNoOptional context for the request - echoed back in response
networkYesNetwork name
blockchainYesBlockchain protocol
sortingOrderNoSort order: ascending (oldest first) or descending (newest first)
startingAfterNoPagination cursor - use nextStartingAfter from previous response

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, open-world), and the description adds behavior they don't: a hard 14-day recency window, the cursor contract (nextStartingAfter → startingAfter), and per-action, per-chain credit costs with the caveat that actual spend is reported in response headers. Cost disclosure is a genuinely useful trait for an agent choosing between five actions with wildly different prices.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

Purpose and pagination are correctly front-loaded, and the blockchain→networks mapping earns its space. However, the five-line credit table dominates the description while being explicitly labeled "indicative only and may change at any time," so a large fraction of the text is low-confidence detail that could be compressed to a single sentence.

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 tool with five distinct actions and no output schema, the description never indicates what each action returns — no mention of a balance object, transaction fields, or token-transfer shape. It covers inputs, cost, and pagination well but leaves the response side largely unexplained.

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 100%, so the baseline is 3; the description goes beyond it by explaining the cross-response semantics of startingAfter, which the schema only hints at. The network-to-blockchain mapping also disambiguates values like sepolia and fuji that appear under multiple chains.

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 opens with a specific verb and resource ("Query latest EVM address data") and bounds scope to the last 14 days. It then enumerates the five actions and the blockchains each supports, which lets an agent separate this tool from the non-EVM siblings (kaspa, solana, utxo, xrp) without opening a schema.

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?

The action×blockchain matrix effectively tells the agent which combinations are legal, which is real selection guidance for a multi-action tool. What's missing is explicit when-not guidance — nothing says whether to prefer a sibling tool or a different endpoint for historical data beyond 14 days.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.