Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

coingecko_global_charts

Fetch CoinGecko global crypto chart time series for total market cap, Bitcoin dominance, altcoin market cap, or DeFi market cap by range and point limit.

Instructions

CoinGecko global chart series. Returns a time series for one global crypto metric from CoinGecko: total market cap (default), Bitcoin dominance, altcoin market cap or DeFi market cap. Choose a range from 24h to max (default 90d) and cap points per series with limit (default 120, max 500). Each point has a timestamp, datetime and value.

Input Schema

NameRequiredDescriptionDefault
kindNoChart kind, default total_market_cap
limitNoRows per series to return, default 120, max 500
rangeNoChart range, default 90d

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.5
    • addedInput schema / properties / kind / enum
      Added value: +[
+  "total_market_cap",
+  "bitcoin_dominance",
+  "altcoin_market_cap",
+  "defi_market_cap"
+]
    • addedInput schema / properties / range / enum
      Added value: +[
+  "24h",
+  "7d",
+  "14d",
+  "30d",
+  "90d",
+  "1y",
+  "max"
+]
  2. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does reasonably well: it discloses the return shape ('timestamp, datetime and value'), the default and max for `limit` (120, max 500), and the default range. It does not mention rate limits, caching, or data freshness, which are the remaining behavioral gaps for a read-only data tool.

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?

Three sentences, zero waste, and front-loaded: the purpose leads, the selectable metrics come next, and the range/limit mechanics plus point shape close it out. Every sentence carries distinct information.

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 3-parameter, no-required-input read tool with no output schema, the definition covers the metric choices, the range/limit constraints, and the shape of each returned point, which is what an agent needs to call it correctly. The only shortfall is the absence of sibling routing against coingecko_global.

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?

Schema description coverage is 100%, so all three parameters are already documented with defaults and enums, making 3 the baseline. The description restates the same defaults and the kind options in prose but adds no extra semantic detail such as what units values are in or how the timestamp is formatted.

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: 'Returns a time series for one global crypto metric from CoinGecko,' and enumerates the exact four metrics available. It is clearly a chart/series tool, but it never names or contrasts with the sibling coingecko_global (the snapshot equivalent), so an agent must infer which of the two to pick for 'current' vs 'historical' data.

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?

It gives concrete usage mechanics — pick a `range` from 24h to max, cap points with `limit`, defaults noted — which implies the intended usage pattern. However, there is no explicit when-to-use-this-vs-alternatives guidance, notably no direction to use coingecko_global for a current single-value snapshot instead of a series.

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