Unlocks for one token
get_token_unlocksAll scheduled unlocks in the next 60 days for one token, with recipients (team, investors, treasury ...), USD value, share of circulating supply, futures availability and a link to the token page. Accepts a ticker (ARB), a name (Arbitrum) or a slug (arbitrum). Matching is exact: matched_by says whether the ticker, the slug or the name matched. A partial match never selects a token; close names come back in did_you_mean. coverage tells three cases apart: in_calendar (unlocks listed); known_no_unlock (we track this token and it has no unlock in the next 60 days, found=0, not an error); unknown_token (the token is not in our data: this is NOT evidence that it has no unlocks, say that we do not cover it). disputed=true on an unlock means the project's own documents give a different amount or date; dispute_summary has both versions and both must be reported. If the result mentions onchain_check, call get_onchain_check to see what the locked wallets are doing. recipient_selling_habit (when present) says how often recipients of this coin's past unlocks sold within 7 days; it is reference only and did not predict price. lang=ru returns Russian page links.
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": {
"token": "<token>"
},
"name": "get_token_unlocks"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| lang | No | en | |
| token | Yes | Ticker, name or slug. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | ||
| found | Yes | ||
| token | No | ||
| source | Yes | ||
| symbol | No | ||
| license | No | ||
| message | No | ||
| unlocks | No | ||
| coverage | Yes | ||
| matched_by | No | ||
| did_you_mean | No | ||
| calendar_page | No | ||
| onchain_check | No | ||
| data_updated_utc | No |