Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

coingecko_news

Fetch recent crypto news cards from CoinGecko with titles, URLs, summaries, publishers, mentioned coins, and price changes for market monitoring.

Instructions

CoinGecko news cards. Returns recent crypto news cards from CoinGecko, up to limit articles (default 20, max 50). Each article has its title, URL, image URL, summary, publisher and published_text, plus the coins it mentions with their id, name, symbol, URL and change_percent when present.

Input Schema

NameRequiredDescriptionDefault
limitNoRows to return, default 20, max 50

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the returned fields in detail (title, URL, image URL, summary, publisher, published_text, and mentioned coins with change_percent), which is valuable given there is no output schema. However, it omits freshness window ('recent' is undefined), pagination behavior, and any rate-limit or auth context.

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?

Two sentences, front-loaded with the core purpose followed by the return shape. The field enumeration is somewhat long but earns its place given there is no output schema. No wasted filler.

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?

For a simple, parameter-light news fetch with no output schema and no annotations, the description is fairly complete: it covers purpose, the limit constraint, and the full article structure. Missing only freshness definition and pagination, which are minor for this tool type.

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?

Only one parameter (limit) with 100% schema description coverage; the description repeats the default (20) and max (50) already stated in the schema. No additional semantics beyond the schema are added, so the baseline of 3 applies.

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?

States a specific verb and resource: 'Returns recent crypto news cards from CoinGecko.' This is unambiguous about what the tool fetches. It does not explicitly distinguish itself from other news-fetching siblings (e.g., coingecko_learn_articles or other *_news tools), keeping it short of a 5.

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?

Usage is implied by the description (fetch recent crypto news), but there is no explicit when-to-use, when-not-to-use, or named alternative. No guidance on whether this is the preferred source over other news tools in the catalog.

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