Skip to main content
Glama

Defi Token Emission

defi_token_emission
Read-onlyIdempotent

One crypto token's full vesting / EMISSION SCHEDULE from DefiLlama (e.g. "Hyperliquid HYPE unlock schedule", "when do Arbitrum team tokens vest"). Returns max supply, allocation by category (insiders, airdrop, staking...) with % unlocked so far, per-recipient unlocked-now vs final amounts, the dated unlock events (past and upcoming, with USD value at the current price), and DefiLlama's methodology notes.

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": {
      "protocol": "hyperliquid"
    },
    "name": "defi_token_emission"
  }
}

Input Schema

NameRequiredDescriptionDefault
protocolYesDefiLlama protocol slug or name (e.g. "hyperliquid", "arbitrum", "aptos", "sui"). Unknown names return close matches.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the description's job is to add context — and it does, enumerating the returned data: max supply, category allocation with % unlocked, per-recipient unlocked-now vs final, dated unlock events valued at current price, and methodology notes. The only missing behavioral detail is freshness/pricing caveats for the USD valuations.

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?

It is one dense but front-loaded sentence: the resource and source come first, then the payload enumeration. Every clause (allocations, per-recipient amounts, unlock events, methodology) describes a distinct part of the response, though the sentence is long enough that a bulleted payload list would scan faster.

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?

With no output schema and only one parameter, the description must carry the return-value burden, and it does so comprehensively — supply, allocation, per-recipient vesting, dated events with USD values, and methodology notes. An agent can decide whether this tool answers a given vesting question without further information.

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?

There is a single parameter with 100% schema coverage, including the slug-or-name hint and the close-match fallback, so the schema already carries the semantics. The description adds only illustrative protocol names through its example queries, which is marginal value over the schema.

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?

The description names a specific resource (one token's vesting/emission schedule) and source (DefiLlama), with concrete example queries that pin down intent. It does not explicitly contrast with the nearby sibling defi_token_unlocks, so an agent must infer the boundary from the richer payload described here (allocations, per-recipient amounts, methodology).

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?

The parenthetical example queries ("Hyperliquid HYPE unlock schedule", "when do Arbitrum team tokens vest") implicitly tell the agent this is for per-token vesting questions. There is no explicit when-not guidance or routing to alternatives such as defi_token_unlocks or defi_protocol_detail.

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.