Skip to main content
Glama

Get how much SOL is still locked in stake account lockups and how much unlocks soon.

solana_unlocks_get_unlock_summary
Read-onlyIdempotent

Get how much SOL is still locked in stake account lockups and how much unlocks soon. Returns the locked SOL total (and the delegated part), the next unlock day, the SOL unlocking in the next 7, 30, 90 and 365 days, and the last unlock date. Use solana_unlocks_get_unlock_calendar for the schedule. Free, no payment needed. 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_get_unlock_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety bar is met structurally. The description adds genuinely useful context beyond that: a free/no-payment cost note and the data provenance (Solana mainnet-beta stake account lockups via JSON-RPC, public on-chain data), which tells the agent about freshness and trustworthiness of results.

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, followed by returned content, the alternative tool, cost, and source. The enumeration of every returned field (7/30/90/365-day buckets, next unlock day, last unlock date) is somewhat long given an output schema exists, but it is scannable and each clause is informative rather than filler.

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?

For a zero-parameter read tool with a full annotation set and an output schema, the description covers everything an agent needs: what it returns in concept, which sibling handles the schedule, that it costs nothing, and where the data comes from. Return-value details are correctly left to the output schema.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly avoids inventing inputs and instead frames the scope of what the no-argument call returns.

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 (Get) and a precise resource: how much SOL remains locked in stake account lockups and how much unlocks soon. It also delineates scope against the named sibling solana_unlocks_get_unlock_calendar (schedule), so an agent can pick between them 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?

Explicitly routes schedule-oriented requests to solana_unlocks_get_unlock_calendar, giving a clear use-case boundary. It does not address the other unlock sibling (list_unlocks) or state exclusions, but the primary alternative is named with its selecting condition.

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