Skip to main content
Glama
IAcomunIA

CoinGecko MCP Server

by IAcomunIA

get_range_coins_market_chart

Read-only

Retrieve historical price, market cap, and volume data for cryptocurrencies within a specified date range using the CoinGecko API.

Instructions

When using this tool, always use the jq_filter parameter to reduce the response size and improve performance.

Only omit if you're sure you don't need the data.

This endpoint allows you to get the historical chart data of a coin within certain time range in UNIX along with price, market cap and 24hr volume based on particular coin ID

Response Schema

{
  $ref: '#/$defs/market_chart_get_range_response',
  $defs: {
    market_chart_get_range_response: {
      type: 'object',
      properties: {
        market_caps: {
          type: 'array',
          items: {
            type: 'array',
            items: {
              type: 'number'
            }
          }
        },
        prices: {
          type: 'array',
          items: {
            type: 'array',
            items: {
              type: 'number'
            }
          }
        },
        total_volumes: {
          type: 'array',
          items: {
            type: 'array',
            items: {
              type: 'number'
            }
          }
        }
      }
    }
  }
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
fromYesstarting date in ISO date string (`YYYY-MM-DD` or `YYYY-MM-DDTHH:MM`) or UNIX timestamp. **use ISO date string for best compatibility**
toYesending date in ISO date string (`YYYY-MM-DD` or `YYYY-MM-DDTHH:MM`) or UNIX timestamp. **use ISO date string for best compatibility**
vs_currencyYestarget currency of market data *refers to [`/simple/supported_vs_currencies`](/reference/simple-supported-currencies).
intervalNodata interval, leave empty for auto granularity
precisionNodecimal place for currency price value
jq_filterNoA jq filter to apply to the response to include certain fields. Consult the output schema in the tool description to see the fields that are available. For example: to include only the `name` field in every object of a results array, you can provide ".results[].name". For more information, see the [jq documentation](https://jqlang.org/manual/).
Behavior3/5

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

Annotations indicate readOnlyHint=true, which the description aligns with by describing a data retrieval operation ('get'). The description adds some behavioral context: it emphasizes performance considerations with 'jq_filter' and mentions the response includes arrays of prices, market caps, and volumes. However, it doesn't disclose other traits like rate limits, authentication needs, or data freshness. With annotations covering safety, a 3 is appropriate as the description adds moderate value beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is somewhat front-loaded with the 'jq_filter' recommendation, but it includes an embedded JSON output schema that is redundant with the context signals (output schema is false in signals, but description includes one). This adds unnecessary length. The core purpose is stated clearly, but the structure could be more streamlined by removing the schema duplication or integrating it better.

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?

Given the tool's complexity (7 parameters, 4 required) and the presence of annotations (readOnlyHint) but no output schema in context signals, the description is moderately complete. It explains the purpose, gives usage tips, and includes an output schema in the description text, which compensates for the missing output schema in signals. However, it lacks details on error handling, data granularity, or how to interpret the response arrays, leaving some gaps for an AI agent.

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 high at 86%, with detailed descriptions for parameters like 'from', 'to', 'vs_currency', 'interval', 'precision', and 'jq_filter'. The description doesn't add significant semantic details beyond the schema, except for strongly recommending 'jq_filter' for performance. Given the high schema coverage, the baseline is 3, as the schema does most of the parameter documentation work.

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 clearly states the tool's purpose: 'get the historical chart data of a coin within certain time range in UNIX along with price, market cap and 24hr volume based on particular coin ID.' It specifies the verb ('get'), resource ('historical chart data'), and key data fields. However, it doesn't explicitly differentiate from sibling tools like 'get_range_coins_ohlc' or 'get_range_contract_coins_market_chart,' which appear to serve similar chart/data retrieval functions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear usage guidance: it strongly recommends using the 'jq_filter' parameter to reduce response size and improve performance, and advises omitting it only if the data is definitely not needed. This gives practical advice on when to use a specific parameter. However, it doesn't specify when to use this tool versus alternative tools for similar data (e.g., 'get_range_coins_ohlc'), nor does it mention prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/IAcomunIA/MCP_firts'

If you have feedback or need assistance with the MCP directory API, please join our Discord server