Skip to main content
Glama

List individual SOL stake account unlocks in a date range, largest first within each time.

solana_unlocks_list_unlocks
Read-onlyIdempotent

List individual SOL stake account unlocks in a date range, largest first within each time. Dates from and to are YYYY-MM-DD, inclusive (default today and 30 days on). Filters: min_sol, withdraw_authority (whose SOL it is) and custodian (who can lift the lockup). Each row gives the stake account, SOL, unlock time, withdraw authority, custodian and the vote account it is delegated to (null if not delegated). Returns up to limit rows (default 50, max 200) and the matched count and SOL. Costs $0.002 per call, paid via x402 in USDC on Base; the first 3 paid-tool calls per day are free for MCP clients while a shared daily allowance lasts. Without x402 support, later calls return the payment requirements as an error result. Failed calls are not charged. Source: Solana mainnet-beta (stake account lockups via JSON-RPC), Public on-chain data.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "solana_unlocks_list_unlocks"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast date, YYYY-MM-DD (default from + 29 days) (e.g. 2026-12-31)
fromNoFirst date, YYYY-MM-DD (default today) (e.g. 2026-12-01)
limitNoRows to return, 1 to 200 (default 50) (e.g. 20)
min_solNoOnly unlocks of at least this many SOL (e.g. 10000)
custodianNoOnly lockups with this custodian (base58)
withdraw_authorityNoOnly stake accounts with this withdraw authority (base58)

Output Schema

NameRequiredDescriptionDefault
dataNoResult: a list of applications for search and nearby tools, one record or summary object otherwise
metaYesPaging and query details, e.g. limit, offset, has_more, count
attributionYesSource attribution; keep it when presenting the data

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses pricing ($0.002 per call via x402 in USDC on Base), a free tier of 3 calls per day, error behavior for clients without x402 support, and that failed calls are not charged. It also names the data source (Solana mainnet-beta, JSON-RPC).

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 purpose, then filters, then row shape, then pagination and cost. Dense but every clause carries information; the payment sentence is long but necessary for calling successfully.

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

Completeness5/5

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

An output schema exists, yet the description still summarizes row fields, matched count and SOL, and covers payment/error paths, so an agent can call it correctly without surprises. Nothing material is missing for a 6-parameter read tool.

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 baseline is 3, but the description adds real meaning: withdraw_authority is glossed as 'whose SOL it is' and custodian as 'who can lift the lockup', which the schema does not convey. It also restates inclusive date semantics and limit bounds, though those duplicate the schema.

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 (list individual SOL stake account unlocks) with scope (date range) and ordering (largest first within each time). The word 'individual' distinguishes it from sibling aggregate tools like get_unlock_calendar and get_unlock_summary.

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?

The description implies usage by emphasizing per-row granularity and describing the filters, but never explicitly says when to pick this over get_unlock_summary or get_unlock_calendar. Prerequisites are only implied (payment setup).

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