Fetch incoming token unlock schedules from CoinGecko. Get normalized rows to monitor potential supply increases.
CoinGecko incoming token unlocks. Returns normalized rows from CoinGecko's public incoming token unlocks page.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Rows to return, default 100, max 100 |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description should disclose behavioral traits. It only states it returns normalized rows from a public page, implying it's a read operation, but fails to mention rate limits, authentication, or any side effects. Minimal behavioral context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loads the source and purpose, and contains no unnecessary words. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple tool with one parameter and no output schema, the description is adequate but incomplete. It does not describe what fields are in the returned rows or what 'incoming token unlocks' means, which could help the agent understand the output.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The single parameter 'limit' is already fully described in the input schema (default 100, max 100). The description adds no additional meaning beyond what the schema provides, so a baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it returns normalized rows from CoinGecko's public incoming token unlocks page. It uses a specific verb ('returns') and resource ('normalized rows'), and distinguishes itself among many CoinGecko sibling tools by focusing on token unlocks.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives. There are many CoinGecko siblings, but the description does not mention any specific context, prerequisites, or when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.