Get normalized article cards from CoinGecko's public news page to track cryptocurrency news. Use the limit parameter to set how many articles you want.
CoinGecko news cards. Returns normalized article cards from CoinGecko's public news page.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Rows to return, default 20, max 50 |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden but only states it returns 'normalized article cards,' lacking details on rate limits, authentication, pagination, or any behavioral traits beyond what is obvious.
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 concise sentences with no redundancy, front-loading the core purpose and including the key parameter constraint.
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?
Given the tool's simplicity (one optional parameter, no output schema), the description is adequate but could benefit from detailing what fields are in a 'normalized article card' or pagination behavior.
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?
Schema coverage is 100% for the single parameter 'limit.' The description's mention of 'default 20, max 50' mirrors the schema description without adding extra meaning, so the baseline of 3 applies.
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 CoinGecko news cards from the public news page, using a specific verb ('Returns') and resource ('normalized article cards'). It distinguishes itself from other coingecko tools like coingecko_search or coingecko_markets.
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?
The description provides no guidance on when to use this tool versus alternatives, no when-not-to-use conditions, and no context for ideal use cases.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.