Skip to main content
Glama
cryptoapis-address-latest

cryptoapis-address-latest

Official

Kaspa address balance and latest activity

kaspa_address_latest
Read-onlyIdempotent

Query Kaspa address balance and transaction history on mainnet, using cursor pagination to page through results.

Instructions

Query latest Kaspa address data. Cursor pagination: use 'nextStartingAfter' from response as 'startingAfter'.

Actions: • get-balance: Get address KAS balance • list-transactions: Get address transactions

Networks: mainnet (only)

Credits by action (source: OpenAPI): • get-balance: kaspa 918 • list-transactions: kaspa 918

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>",
      "network": "<network>",
      "address": "<address>"
    },
    "name": "kaspa_address_latest"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of items to return (max 50)
actionYesAction to perform: get-balance, list-transactions
addressYesKaspa address to query
contextNoOptional context for the request - echoed back in response
networkYesNetwork name: mainnet (only mainnet available)
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 and non-destructive, so the bar is lower, and the description still adds real context: per-action credit cost, the caveat that actual credits are returned in response headers, and the cursor-chaining contract. It stops short of describing what a balance or transaction record looks like, which matters since there is no output schema.

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?

Front-loads purpose, then bullets the two actions, then the network constraint and credit costs in short labeled blocks. The dual 'Credits by action' plus 'Credits are indicative only' lines are slightly redundant but still earn their place as cost disclosure.

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?

Covers purpose, actions, network, pagination and cost adequately for a read-only query tool with full schema coverage. The notable gap is that with no output schema the description does not say what get-balance or list-transactions return, and it leaves the agent to infer which optional parameters belong to which action.

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 all seven parameters are already documented, including the startingAfter cursor hint the description repeats. The description adds no per-action parameter mapping (e.g. that limit and sortingOrder are meaningful only for list-transactions), so it stays at the baseline.

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?

States a specific verb and resource (query Kaspa address data) and enumerates the two concrete actions, get-balance and list-transactions, so the agent knows exactly what operations are available. The chain name in the tool and description also separates it from the evm_/solana_/utxo_/xrp_ siblings without needing their schemas.

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?

Gives useful operational guidance for pagination ('use nextStartingAfter from response as startingAfter') and constrains the network to mainnet. However, it never says when to pick this tool over the sibling chain tools, nor which actions the optional limit/sortingOrder parameters apply to; usage is implied by the action list rather than stated.

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