Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

coingecko_global_charts

Retrieve normalized CoinGecko global chart series as JSON, covering total market cap, Bitcoin dominance, altcoin and DeFi market cap for selected ranges.

Instructions

CoinGecko global chart series. Returns normalized global chart series from public CoinGecko website JSON endpoints.

Input Schema

TableJSON 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

B3.2/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It discloses that the data is 'normalized' and comes from 'public CoinGecko website JSON endpoints,' implying no auth and a consistent format. However, it does not mention rate limits, pagination, default behavior, or error handling, leaving key operational details undisclosed.

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?

The description is concise and front-loaded, consisting of two sentences that state the purpose and a key attribute (normalized, public). No filler or redundant information. It is efficient, though it could use the space to also address usage guidelines or output format.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has no output schema, so the description should clarify the shape of the returned data. It only says 'normalized global chart series,' which is vague about whether it's an array of points, time series format, etc. The tool is relatively simple, but without output schema or more detail, an agent may not know what to expect or how to interpret the result.

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 (kind, limit, range) are already documented with descriptions and enums. The description adds no parameter-specific meaning beyond what the schema provides. Per the calibration rule, the baseline is 3 for high coverage, and there is no extra semantic enrichment.

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 uses a specific verb ('returns') and resource ('CoinGecko global chart series'), and clarifies it returns normalized data from public JSON endpoints. This is distinct from siblings like coingecko_chain or coingecko_categories, though it could be more explicit about what 'global chart' encompasses (e.g., market cap, dominance). The name and schema enums further clarify scope.

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 guidance on when to use this tool versus alternatives, nor any mention of appropriate scenarios. The description only states what it does, not the context in which it is preferred. This is a significant gap given the large sibling list of tools.

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