Skip to main content
Glama

Get the SOL unlock schedule by day, week or month for a date range.

solana_unlocks_get_unlock_calendar
Read-onlyIdempotent

Get the SOL unlock schedule by day, week or month for a date range. Dates from and to are YYYY-MM-DD, inclusive (default today and 90 days on, span up to 1,500 days). The group parameter is day (default), week (starting Monday) or month. Each period gives the SOL whose stake lockup ends then, the number of stake accounts, the delegated part (needs about one epoch to deactivate before withdrawal) and the largest single account. Periods with nothing unlocking are left out. 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_get_unlock_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast date, YYYY-MM-DD (default from + 89 days) (e.g. 2027-05-31)
fromNoFirst date, YYYY-MM-DD (default today) (e.g. 2026-12-01)
groupNoday, week or month (default day) (e.g. month)

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.2/5.0
Behavior5/5

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

Beyond the read-only/idempotent annotations it discloses the paid model ($0.002 per call via x402 in USDC on Base), a free tier of 3 calls/day subject to a shared allowance, the error shape when x402 is unsupported, and the fact that failed calls are not charged. It also explains that empty periods are omitted and that the delegated portion needs roughly one epoch to deactivate, which changes how results should be read.

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?

Purpose and grouping are front-loaded in the first sentence, and the pricing/payment caveats are held for the end. It is dense and multi-clause, but nearly every clause carries information an agent needs; the one avoidable wrinkle is the 90-vs-89-day mismatch with the schema.

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

Completeness4/5

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

With an output schema present, the description rightly stops short of documenting return values but still explains what each period contains and how to interpret the delegated figure. Payment, defaults and span limits are all covered; the only ambiguity left is the slight default-range discrepancy with the 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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: dates are inclusive, weeks start on Monday, and each output period carries the SOL amount, stake account count, delegated portion and largest account. Minor friction: the description says the default range is '90 days on' while the schema says 'from + 89 days', a small inconsistency an agent must resolve.

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 ('Get the SOL unlock schedule') plus the aggregation dimension (day/week/month) and the date-range scope, which is enough to distinguish it from a flat unlock list. It does not explicitly name a sibling (e.g. list_unlocks vs. unlock_summary) to anchor the difference, so differentiation is implied rather than stated.

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?

Gives concrete operating context: defaults (today, 90 days on), a hard span cap of 1,500 days, and the week-start convention for grouping. It never says when to prefer this over the sibling summary or list tools, so an agent still has to infer the choice from the aggregation semantics.

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