Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

coingecko_coin_analysis

Analyze CoinGecko coin price charts and return derived chart metrics from public JSON; specify coin id, range, and quote currency to study historical or 24h trends.

Instructions

CoinGecko coin chart analysis. Returns derived price-chart metrics from CoinGecko public chart JSON. This endpoint supports the documented vs_currency enum and is not investment advice or real-time trading data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesCoinGecko coin id such as bitcoin
rangeNoChart range
vs_currencyNoQuote currency
include_annotationsNoFetch optional CoinGecko chart annotations

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.5
    • addedInput schema / properties / range / enum
      Added value: +[
+  "24h",
+  "max"
+]
    • addedInput schema / properties / vs_currency / enum
      Added value: +[
+  "btc",
+  "eth",
+  "ltc",
+  "bch",
+  "bnb",
+  "eos",
+  "xrp",
+  "xlm",
+  "link",
+  "dot",
+  "yfi",
+  "sol",
+  "usd",
+  "aed",
+  "ars",
+  "aud",
+  "bdt",
+  "bhd",
+  "bmd",
+  "brl",
+  "cad",
+  "chf",
+  "clp",
+  "cny",
+  "czk",
+  "dkk",
+  "eur",
+  "gbp",
+  "gel",
+  "hkd",
+  "huf",
+  "idr",
+  "ils",
+  "inr",
+  "jpy",
+  "krw",
+  "kwd",
+  "lkr",
+  "mmk",
+  "mxn",
+  "myr",
+  "ngn",
+  "nok",
+  "nzd",
+  "php",
+  "pkr",
+  "pln",
+  "rub",
+  "sar",
+  "sek",
+  "sgd",
+  "thb",
+  "try",
+  "twd",
+  "uah",
+  "vef",
+  "vnd",
+  "zar",
+  "xdr",
+  "xag",
+  "xau",
+  "bits",
+  "sats"
+]
  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 provided, the description carries the burden. It adds a useful disclaimer that the data is not real-time trading data or investment advice and notes it is derived from public chart JSON, implying a read-only analytical operation. However, it doesn't disclose rate limits, authentication, data freshness, or what happens on unsupported ids, leaving key behavioral traits unstated.

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 short and front-loaded with the tool's purpose. The last sentence, however, is partially redundant—mentioning the vs_currency enum repeats the schema—and could be trimmed to just the disclaimer.

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, yet the description only vaguely says 'derived price-chart metrics' without enumerating what those are. With no annotations and many Coingecko siblings, the description doesn't fully situate the tool's exact output or when to use it, although the input parameters are well-covered by the schema.

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?

The schema describes all four parameters, so the baseline is 3. The description adds little: it only refers to the documented vs_currency enum and doesn't explain id, range, or include_annotations beyond the schema. No extra semantics are needed to call the tool correctly, but none are provided.

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?

Description states a specific verb ('Returns derived price-chart metrics') and resource ('CoinGecko coin chart'), which conveys the core function. It separates the tool from other Coingecko siblings by focusing on chart metrics, but it doesn't name any sibling or explicitly state what it is not, so it falls short of full differentiation.

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?

No guidance is given for when to choose this tool over other Coingecko analysis tools such as coingecko_global_charts or coingecko_coin. The description only says what the endpoint does and a disclaimer; it never mentions alternatives, exclusions, or recommended use cases.

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