Skip to main content
Glama
cryptoapis-address-latest

cryptoapis-address-latest

Official

Solana address balance and latest activity

solana_address_latest
Read-onlyIdempotent

Query recent Solana address data to retrieve SOL balance, transactions, or SPL token holdings on mainnet or devnet, with cursor pagination for up to 14 days of activity.

Instructions

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

Actions: • get-balance: Get address SOL balance • list-transactions: Get address transactions • list-tokens: Get SPL tokens held by address

Networks: mainnet, devnet

Credits by action (source: OpenAPI): • get-balance: solana 75 • list-tokens: solana 120 • list-transactions: solana 90

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

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of items to return (max 50)
actionYesAction to perform: get-balance, list-transactions, list-tokens
addressYesSolana address to query
contextNoOptional context for the request - echoed back in response
networkYesNetwork name: mainnet or devnet
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.6/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint). The description adds genuinely new behavioral facts: a 14-day lookback limit, cursor-pagination mechanics, and per-action credit costs with a caveat that actual credits appear in response headers. It does not describe the response payload shape, 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-loaded with the core purpose and scope, then cleanly bulleted actions, networks, and costs. The credit disclaimer sentence is somewhat boilerplate but is relevant to invocation cost. No redundant restatement of the tool name.

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?

Adequate for a read-only composite query tool, but with no output schema the description says nothing about what balance or transaction records look like, nor default values for limit/sortingOrder. For a seven-parameter, three-action tool the return-side description is thin.

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, and the description's pagination note largely restates the 'startingAfter' schema text. It adds no meaning for 'limit', 'sortingOrder', or 'context', nor does it say which actions those parameters apply to. Baseline 3 is appropriate.

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 specific verb and resource ("Query latest Solana address data") with a scoping constraint (last 14 days) and enumerates the three concrete actions it bundles (get-balance, list-transactions, list-tokens). The Solana focus implicitly separates it from the evm/kaspa/utxo/xrp siblings, though it never explicitly contrasts with them.

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?

Each action is defined well enough to choose between them: need a balance -> get-balance, need history -> list-transactions, need holdings -> list-tokens. It also gives operational guidance on the pagination loop (use 'nextStartingAfter' from response as 'startingAfter'). It stops short of stating when not to use this tool (e.g., historical windows beyond 14 days) or naming an alternative sibling.

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