Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

coingecko_token_unlocks

Fetch upcoming token unlock events from CoinGecko via Crawlora MCP, with supply released, next unlock amount, USD value, and time remaining for up to 100 coins.

Instructions

CoinGecko incoming token unlocks. Returns CoinGecko's list of upcoming token unlocks, up to 100 rows. Each row has the coin's name, symbol, rank, price, 1-hour, 24-hour and 7-day change and market cap, the share of supply already released, and the next unlock's amount, percentage, USD value and time remaining.

Input Schema

NameRequiredDescriptionDefault
limitNoRows to return, default 100, max 100

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It discloses that this is a read-style retrieval returning upcoming token unlocks, capped at 100 rows, and it enumerates the row fields, but it does not mention authentication, rate limits, ordering, freshness, or other operational traits.

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?

Two sentences, front-loaded with the source and resource, then the return shape. Every clause earns its place by either identifying the tool or describing the output.

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?

Because there is no output schema, the description appropriately explains what each returned row contains. For a low-complexity, one-parameter data retrieval tool, this is nearly complete, though usage guidance and operational details remain thin.

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 schema has 100% description coverage for the single 'limit' parameter, so the baseline is 3. The description's phrase 'up to 100 rows' aligns with the max but does not add syntax, default behavior, or other meaning beyond what the schema already documents.

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 states a specific CoinGecko resource: upcoming/incoming token unlocks, and the main action is effectively 'Returns ... list of upcoming token unlocks.' This is clear and specific, though it does not explicitly contrast itself with the many other CoinGecko sibling tools.

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

Usage Guidelines2/5

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

The description does not say when to use this tool versus alternatives, nor does it provide explicit when-not conditions. Usage is only implied by the resource name and the word 'upcoming'.

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

Deploy Server

Other Tools