Skip to main content
Glama
IAcomunIA

CoinGecko MCP Server

by IAcomunIA

get_range_contract_coins_market_chart

Read-only

Retrieve historical cryptocurrency price, market cap, and volume data for specific token contracts within a defined time range using the CoinGecko MCP Server.

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 within certain time range in UNIX along with price, market cap and 24hr volume based on asset platform and particular token contract address

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
contract_addressYes
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?

The annotation 'readOnlyHint: true' already indicates this is a safe read operation. The description adds useful behavioral context: it emphasizes performance optimization with 'jq_filter', mentions the response contains arrays of numbers for market data, and specifies the tool is for historical data within a time range. However, it doesn't disclose other behavioral traits like rate limits, authentication needs, or data freshness that aren't covered by annotations.

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 appropriately sized and front-loaded with critical usage advice about 'jq_filter'. The second sentence clearly states the tool's purpose. However, the inclusion of the full output schema within the description text is redundant and adds unnecessary length, as this information should be in a separate structured field.

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 complexity (8 parameters, historical data query) and the presence of annotations (readOnlyHint) but no output schema, the description is moderately complete. It covers the core purpose and key behavioral advice about response filtering, but doesn't explain the structure of returned arrays (e.g., that each inner array contains [timestamp, value] pairs) or provide guidance on parameter combinations. The embedded output schema partially compensates for the missing structured output 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?

Schema description coverage is 75%, so the schema already documents most parameters well. The description adds marginal value by mentioning 'asset platform' (implied by 'id' parameter) and 'particular token contract address' (matching 'contract_address'), but doesn't explain parameter interactions or provide additional semantics beyond what's in the schema. With high schema coverage, the baseline score of 3 is appropriate.

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 within certain time range in UNIX along with price, market cap and 24hr volume based on asset platform and particular token contract address.' It specifies the verb ('get'), resource ('historical chart data'), and key parameters (time range, asset platform, contract address). However, it doesn't explicitly differentiate from similar siblings like 'get_range_coins_market_chart' or 'get_nfts_market_chart' beyond mentioning 'contract address'.

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 explicit guidance on when to use the 'jq_filter' parameter ('always use... to reduce response size and improve performance') and when to omit it ('Only omit if you're sure you don't need the data'). It also implies usage context by specifying the data types (price, market cap, volume) and that it's for historical chart data. However, it doesn't mention when to choose this tool over alternatives like 'get_range_coins_market_chart' or 'get_simple_price'.

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