mcp-livedatapro

getTokenUnlocks

Upcoming venture capital and team token unlock schedules, cliff dates, and circulating supply inflation impact. Use when tracking upcoming cryptocurrency vesting cliff dates, VC/team token unlock amounts, USD value impact, and circulating supply inflation percentages. Do not use for live DEX pool liquidity or honeypot checks (use getCryptoDexLiquidity).

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_symbol": "<token_symbol>"
    },
    "name": "getTokenUnlocks"
  }
}

Input Schema

Name	Required	Description	Default
`token_symbol`	Yes	Uppercase cryptocurrency token ticker symbol (e.g., ARB, OP, SUI, SOL).

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 24, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / token_symbol / examples
```
Added value: +[
+  "ARB"
+]
```
- addedInput schema / properties / token_symbol / pattern
```
Added value: +"^[A-Z0-9]{2,10}$"
```

Changed1 schema field changedOct 24, 2026

changedInput schema / properties / token_symbol / description

Previous value: -"Crypto token symbol (e.g., OP, ARB, SUI, SOL)"New value: +"Uppercase cryptocurrency token ticker symbol (e.g., ARB, OP, SUI, SOL)."

First observedOct 21, 2026

TDQS

A4.3/5.0

Behavior3/5

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

With no annotations, the description must carry the full behavioral burden. It describes the content returned (unlock schedules, cliff dates, USD impact, inflation percentages) but does not disclose operational traits like data freshness, rate limits, or authentication requirements. Since it is a read-only lookup tool, the lack of safety hints is less critical, but these gaps keep it at a 3.

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?

The description is concise and front-loaded: it leads with the core data offered, then states usage, then a clear exclusion with a sibling alternative. Every sentence contributes useful routing information with no wasted text.

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?

Given the tool's low complexity (one parameter, 100% schema coverage, no output schema), the description is complete enough. It explains what data is returned (unlock schedules, cliff dates, USD value, inflation percentages) and how it relates to a sibling tool, so an agent can decide when and how to call it correctly.

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?

The input schema has 100% description coverage for the single token_symbol parameter, including pattern and examples. The description does not add any syntax or format details beyond what the schema already provides, so the baseline 3 is appropriate.

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?

The description states a specific resource and scope: venture capital and team token unlock schedules, cliff dates, and circulating supply inflation impact. It clearly distinguishes itself from the sibling getCryptoDexLiquidity by naming it as an alternative for other use cases.

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

Usage Guidelines5/5

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

It explicitly says when to use it: tracking upcoming cryptocurrency vesting cliff dates, VC/team token unlock amounts, USD value impact, and circulating supply inflation percentages. It also explicitly says when not to use it and names the correct alternative tool (getCryptoDexLiquidity) for those excluded cases.

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

All mcp-livedatapro 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.

Resources

Need Help?