Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

coingecko_global

Fetch a global cryptocurrency market snapshot with total market cap, 24-hour and 1-year changes, Bitcoin and Ethereum dominance, stablecoin share, and tracked coin, exchange, and category counts.

Instructions

CoinGecko global market snapshot. Returns CoinGecko's global crypto market snapshot: total market cap in USD with its 24-hour and 1-year change, Bitcoin market cap, Bitcoin and Ethereum dominance, stablecoin market cap and share, and the number of coins, exchanges and categories tracked. Takes no parameters.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations and no output schema, the description carries the full burden, and it does disclose the complete return payload field-by-field, which is genuinely useful behavioral context. It does not mention data freshness/caching, snapshot timestamp, or rate limits, so it is not exhaustive, but for a zero-parameter read-only tool the disclosure is strong.

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 payload list in the second. The first sentence ('CoinGecko global market snapshot') is largely restated by the opening of the second ('Returns CoinGecko's global crypto market snapshot'), a small redundancy, but the rest earns its space.

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?

No output schema exists, so the description must describe the return, and it enumerates every metric returned — sufficient for an agent to call and interpret the tool. Minor gaps remain (currency fixed to USD is stated, but no snapshot timestamp or refresh cadence).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Zero parameters, so the baseline is 4. The description explicitly confirms 'Takes no parameters', removing any doubt that the agent should pass arguments or expect filtering options.

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 verb and resource: it returns CoinGecko's global crypto market snapshot, then enumerates the exact metrics (total market cap with 24h/1y change, BTC market cap, BTC/ETH dominance, stablecoin share, counts). That is far more specific than a tautology. It stops short of 5 because it never names or contrasts the obvious sibling, coingecko_global_charts, which also covers global market data.

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?

There is no when-to-use or when-not-to-use guidance, and no alternative is named. The only routing signal is 'Takes no parameters', which the agent must interpret as 'use this when you want the current aggregate and don't need history' — inference rather than guidance.

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