Skip to main content
Glama

Defi Token Unlocks

defi_token_unlocks
Read-onlyIdempotent

Crypto token UNLOCK calendar from DefiLlama: every scheduled vesting cliff and emission-rate change across ~370 tracked tokens in a date window (e.g. "which token unlocks are scheduled this week", "unlocks over $10M between 2026-10-05 and 2026-10-12"). Returns per event: date, token, tokens unlocked, USD value at the current DefiLlama price (with the price time), share of circulating supply, and the recipients (investors, team, ecosystem...). Default window is today through 7 days out.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "to": "2026-10-12",
      "from": "2026-10-05"
    },
    "name": "defi_token_unlocks"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoWindow end, YYYY-MM-DD (UTC, inclusive). Default: from + 7 days.
fromNoWindow start, YYYY-MM-DD (UTC, inclusive). Default: today.
limitNoMax events returned, sorted by date then USD value (default 100, max 500).
tokenNoRestrict to tokens whose name, symbol or DefiLlama slug contains this text (e.g. "hyperliquid", "ARB").
searchNoAlias of token.
min_usdNoOnly cliff unlocks worth at least this many USD at the current price (e.g. 1000000). Excludes emission-rate changes, which have no single USD amount.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / search
      Added value: +{
      +  "description": "Alias of token.",
      +  "type": "string"
      +}
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior, so the bar is lower; the description then adds real context: the default 7-day window, the per-event return shape, and that USD values use DefiLlama's price with the price timestamp. It does not discuss rate limits or result cap behavior beyond what the schema states.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense paragraph, front-loaded with the resource and scope, then the return contract, then the default window. Every clause carries information an agent would otherwise have to infer.

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 no output schema, the description usefully enumerates the returned fields (date, token, tokens unlocked, USD value, supply share, recipients), and the annotations cover the safety profile. Minor omission: sorting/limit behavior is left entirely to the schema, but overall nothing essential is missing.

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

Parameters3/5

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

Schema description coverage is 100%, so all six parameters are already documented, including the today/+7-day defaults and the note that min_usd excludes emission-rate changes. The description restates the default window but adds no parsing hints, syntax, or interaction detail beyond the schema; baseline 3 applies.

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 concrete verb and resource: a token-unlock/vesting calendar from DefiLlama covering ~370 tokens within a date window, with the returned fields spelled out. It distinguishes the resource clearly from other Defi data tools, though it never names a sibling such as defi_token_emission to route the agent explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is conveyed only through example phrasings ("which token unlocks are scheduled this week", "unlocks over $10M between dates"), which imply when the tool fits. There is no explicit when-not guidance and no named alternative for emission-rate-specific questions, which is notable given the sibling defi_token_emission.

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.