Skip to main content
Glama

Unlocks for one token

get_token_unlocks
Read-only

All 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

NameRequiredDescriptionDefault
langNoen
tokenYesTicker, name or slug.

Output Schema

NameRequiredDescriptionDefault
nameNo
foundYes
tokenNo
sourceYes
symbolNo
licenseNo
messageNo
unlocksNo
coverageYes
matched_byNo
did_you_meanNo
calendar_pageNo
onchain_checkNo
data_updated_utcNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changed
    • addedOutput schema / properties / coverage
      Added value: +{
      +  "enum": [
      +    "in_calendar",
      +    "known_no_unlock",
      +    "unknown_token"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / did_you_mean
      Added value: +{
      +  "items": {
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / matched_by
      Added value: +{
      +  "enum": [
      +    "symbol",
      +    "slug",
      +    "name",
      +    null
      +  ],
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / name
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / symbol
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / unlocks / items / properties / aggregator_share_of_total_supply_pct
      Added value: +{
      +  "type": [
      +    "number",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / unlocks / items / properties / date_source_url
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / unlocks / items / properties / dispute_reason
      Added value: +{
      +  "enum": [
      +    "amount_differs",
      +    "date_differs"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / unlocks / items / properties / dispute_summary
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / unlocks / items / properties / disputed
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / unlocks / items / properties / numbers_from
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / unlocks / items / properties / range_note
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / unlocks / items / properties / share_of_circulating_pct_by_documents
      Added value: +{
      +  "type": [
      +    "number",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / unlocks / items / properties / strength_by_documents
      Added value: +{
      +  "enum": [
      +    "strong",
      +    "medium",
      +    "small"
      +  ],
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "source",
      -  "found"
      -]New value: +[
      +  "source",
      +  "found",
      +  "coverage"
      +]
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "calendar_page": {
      +      "type": "string"
      +    },
      +    "data_updated_utc": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "found": {
      +      "type": "number"
      +    },
      +    "license": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "message": {
      +      "type": "string"
      +    },
      +    "onchain_check": {
      +      "type": "string"
      +    },
      +    "source": {
      +      "type": "string"
      +    },
      +    "token": {
      +      "type": "string"
      +    },
      +    "unlocks": {
      +      "items": {
      +        "properties": {
      +          "add_to_calendar": {
      +            "type": "string"
      +          },
      +          "already_unlocked_pct": {
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "data_source": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "date_confirmed": {
      +            "type": "boolean"
      +          },
      +          "date_note": {
      +            "type": "string"
      +          },
      +          "date_utc": {
      +            "type": "string"
      +          },
      +          "days_left": {
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "fdv_usd": {
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "hours_left": {
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "kind": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "liquidity_note": {
      +            "type": "string"
      +          },
      +          "market_cap_usd": {
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "name": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "page": {
      +            "type": "string"
      +          },
      +          "perpetual_futures_on": {
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": "array"
      +          },
      +          "price_change_7d_pct": {
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "primary_source_check": {
      +            "type": "object"
      +          },
      +          "recipient_selling_habit": {
      +            "type": "object"
      +          },
      +          "recipients": {
      +            "type": "array"
      +          },
      +          "recipients_detail": {
      +            "type": "array"
      +          },
      +          "share_of_circulating_pct": {
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "share_of_circulating_range_pct": {
      +            "items": {
      +              "type": "number"
      +            },
      +            "type": "array"
      +          },
      +          "share_of_total_supply_pct": {
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "strength": {
      +            "enum": [
      +              "strong",
      +              "medium",
      +              "small"
      +            ],
      +            "type": "string"
      +          },
      +          "symbol": {
      +            "type": "string"
      +          },
      +          "value_usd": {
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "volume_24h_usd": {
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "warning": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "symbol",
      +          "date_utc",
      +          "strength",
      +          "page"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "source",
      +    "found"
      +  ],
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds substantial behavior beyond that: exact-match-only resolution with matched_by and did_you_mean, the three coverage states and their epistemic meaning, disputed unlocks requiring both versions to be reported, and the caveat that recipient_selling_habit is reference only. This is exactly the interpretive context annotations cannot carry.

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 capability, then layered with interpretation rules; nearly every sentence carries operational value. It is a dense single block, and the coverage/dispute rules could be split for scannability, but there is little 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?

An output schema exists, yet the description still supplies the semantics needed to act on it (coverage states, disputed handling, did_you_mean, the onchain_check handoff). For a read-only lookup with two parameters, nothing an agent needs to call or interpret it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50% (lang has an enum but no description), and the description compensates: it explains that token accepts ticker/name/slug, that matching is exact, and how matched_by reports which form matched. It also documents the effect of lang=ru (Russian page links), which the schema does not.

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 ('All scheduled unlocks in the next 60 days for one token') plus the payload contents (recipients, USD value, share of circulating supply, futures availability, link). The 60-day window and single-token scope distinguish it from a bulk upcoming-unlocks sibling.

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 clear routing: call get_onchain_check when the result mentions onchain_check, and it explains how to interpret each coverage case rather than treating unknown_token as an error. It does not explicitly contrast with get_upcoming_unlocks or get_disputed_unlocks, so the sibling-selection guidance is implied rather than stated.

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.