Skip to main content
Glama
cryptoapis-address-latest

cryptoapis-address-latest

Official

UTXO address balance and latest activity

utxo_address_latest
Read-onlyIdempotent

Query recent UTXO address balances, confirmed transactions, and mempool activity across Bitcoin, Litecoin, Dogecoin, Dash, Zcash, and Bitcoin Cash for the last 14 days.

Instructions

Query latest UTXO address data (last 14 days). • get-balance: no pagination • list-transactions: cursor pagination - use 'nextStartingAfter' from response as 'startingAfter' • list-unconfirmed-transactions: offset pagination - use 'limit' and 'offset' (lists unconfirmed/mempool transactions)

Actions & supported blockchains: • get-balance: bitcoin, bitcoin-cash, litecoin, dash, dogecoin, zcash • list-transactions: bitcoin, bitcoin-cash, dash, dogecoin, litecoin, zcash • list-unconfirmed-transactions: bitcoin, bitcoin-cash, litecoin, dogecoin, dash, zcash

Blockchain → Networks: • bitcoin: mainnet, testnet • bitcoin-cash: mainnet, testnet • litecoin: mainnet, testnet • dogecoin: mainnet, testnet • dash: mainnet, testnet • zcash: mainnet, testnet

Credits by action (source: OpenAPI): • get-balance: bitcoin 510, bitcoin-cash 612, dash 561, dogecoin 561, litecoin 561, zcash 663 • list-transactions: bitcoin 110, bitcoin-cash 132, dash 121, dogecoin 121, litecoin 121, zcash 143 • list-unconfirmed-transactions: bitcoin 110, bitcoin-cash 132, dash 121, dogecoin 121, litecoin 121, zcash 143

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

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of items to return (max 50)
actionYesAction to perform: get-balance, list-transactions, list-unconfirmed-transactions
offsetNoPagination offset
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

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, non-destructive, so the safety profile is covered. The description still adds real behavior beyond them: the 14-day data window, the distinct pagination mechanics per action, credit costs per action/blockchain, and the note that actual credits are returned in response headers and are subject to change. It says nothing about failure modes (invalid address, unsupported chain/network combination).

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?

The header and action/pagination bullets are front-loaded and useful, but the 'Actions & supported blockchains' list, the 'Blockchain → Networks' list, and the credits block restate the same six blockchains three times with near-identical content, making the description noticeably longer than needed.

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 9-parameter, multi-action tool with no output schema, the description covers action selection, pagination, and cost, which is substantial. It stops short of describing what each action returns (balance fields, transaction record shape) or error behavior, so an agent still cannot anticipate the response payload.

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, but the description goes beyond the field-level docs by tying parameters to actions — startingAfter only for cursor pagination, limit/offset only for offset pagination, and no pagination for get-balance. It does not clarify whether limit/offset are ignored or rejected for get-balance, nor how sortingOrder interacts with pagination.

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 opens with a specific verb and resource ('Query latest UTXO address data') and enumerates the three actions and the six UTXO blockchains it covers, which implicitly separates it from the evm/solana/xrp/kaspa siblings. The only ambiguity is the parenthetical '(last 14 days)', which never explains whether it is a data-retention window or a default query range.

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?

It gives per-action guidance: get-balance takes no pagination, list-transactions uses a cursor ('nextStartingAfter' → 'startingAfter'), and list-unconfirmed-transactions uses limit/offset and is explicitly scoped to mempool transactions. It does not say when to choose this tool over a sibling chain tool or what to do when an address is not a UTXO chain, but the guidance for choosing among the three actions is concrete.

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