MangroveAI

get_token_unlocks

Read-onlyIdempotent

Upcoming token unlocks and supply metrics -- which tokens release supply in the next days_ahead days, when, and how much (cliff amounts and USD value). Heavy near-term unlocks are a supply-shock signal. Pass symbol (the token ticker, case-insensitive) or protocol (also for tokens without a ticker) to ask about specific tokens; a matched token is returned even when its next unlock is outside the window. Results are one page of tokens: limit 1-100 (default 25), offset 0-10000; pass next_offset from a response to get the next page. Use it when the user asks about unlocks, vesting or supply overhang.

[Access: pay 0.01 USDC via x402 (PAYMENT-SIGNATURE header) OR authenticate with an API key. An x402-capable client will auto-pay; API-key clients pay nothing per call.]

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

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum results.
`offset`	No	Pagination offset in the result units documented by the tool; zero starts the first page.
`symbol`	No	Asset symbol, e.g. BTC or ETH.
`rank_by`	No	next_unlock (soonest first) or cliff_value_usd (largest USD value of cliff unlocks in the window first).	next_unlock
`protocol`	No	Protocol or token name, DefiLlama slug or CoinGecko id, case-insensitive exact match.
`days_ahead`	No	Window length in days from now. Without symbol or protocol, only tokens with a scheduled unlock in this window are returned.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedNov 5, 2026

addedInput schema / properties / days_ahead

Added value: +{
+  "default": 30,
+  "description": "Window length in days from now. Without symbol or protocol, only tokens with a scheduled unlock in this window are returned.",
+  "maximum": 365,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / limit

Added value: +{
+  "default": 25,
+  "description": "Maximum results.",
+  "type": "integer"
+}

addedInput schema / properties / offset

Added value: +{
+  "default": 0,
+  "description": "Pagination offset in the result units documented by the tool; zero starts the first page.",
+  "type": "integer"
+}

addedInput schema / properties / protocol

Added value: +{
+  "description": "Protocol or token name, DefiLlama slug or CoinGecko id, case-insensitive exact match.",
+  "type": "string"
+}

addedInput schema / properties / rank_by

Added value: +{
+  "default": "next_unlock",
+  "description": "next_unlock (soonest first) or cliff_value_usd (largest USD value of cliff unlocks in the window first).",
+  "enum": [
+    "next_unlock",
+    "cliff_value_usd"
+  ],
+  "type": "string"
+}

addedInput schema / properties / symbol

Added value: +{
+  "description": "Asset symbol, e.g. BTC or ETH.",
+  "type": "string"
+}

First observedOct 22, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing the access model (0.01 USDC via x402 PAYMENT-SIGNATURE header, or free with an API key) and that x402-capable clients auto-pay — exactly the kind of auth/cost context the annotations cannot express. It also discloses the non-obvious matching rule that a matched token is returned even when its next unlock falls outside the window, which materially affects result interpretation.

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 behavior, then parameter guidance, then access — a sensible order with no filler sentences. It is dense and long-ish for a single description, and the interpretive line about supply-shock signals is nice-to-have rather than required, which keeps it just under 5.

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?

There is no output schema, and the description compensates by explaining that results are one page of tokens with a next_offset to continue, and what the payload measures (cliff amounts and USD value). It stops short of enumerating per-token record fields, but the paging contract and ranking options are covered well enough to call it correctly.

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 already 100%, so the baseline is 3; the description still adds value by supplying concrete bounds the schema omits or states thinly — limit 1-100 (default 25) and offset 0-10000 — plus the next_offset round-trip pattern for paging. It also clarifies that symbol is case-insensitive and that protocol is the fallback for tokens without a ticker.

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 ("Upcoming token unlocks and supply metrics") and then decomposes it into the three things it answers: which tokens, when, and how much. Sibling tools like get_token_holders, get_treasuries, and get_token_flows cover adjacent supply/ownership data, and the vesting/unlock framing here clearly separates this tool from 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?

Explicitly routes the agent with "Use it when the user asks about unlocks, vesting or supply overhang," and additionally explains the two calling modes (filtered by symbol/protocol vs. unfiltered window scan). It does not name a competing sibling or state any when-not condition, which keeps it short of a 5.

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

All MangroveAI tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.