Skip to main content
Glama
IAcomunIA

CoinGecko MCP Server

by IAcomunIA

get_range_coins_ohlc

Read-only

Retrieve OHLC (Open, High, Low, Close) price data for a cryptocurrency within a specified date range to analyze historical price movements and trends.

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 OHLC chart (Open, High, Low, Close) of a coin within a range of timestamp based on particular coin ID

Response Schema

{
  $ref: '#/$defs/ohlc_get_range_response',
  $defs: {
    ohlc_get_range_response: {
      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**
intervalYesdata interval
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 price data *refers to [`/simple/supported_vs_currencies`](/reference/simple-supported-currencies).
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/).
Behavior4/5

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

The annotations provide readOnlyHint=true, indicating this is a safe read operation. The description adds valuable behavioral context beyond annotations: it emphasizes performance optimization with jq_filter, warns about response size, and clarifies the data type (OHLC chart). However, it doesn't mention rate limits, authentication needs, or error handling. Given the annotations cover safety, the description adds useful operational advice, earning a score above baseline.

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 structured with a performance tip first, followed by the core purpose. However, it includes a redundant 'Response Schema' section that duplicates output information without adding value, as there's no output schema provided. The text could be more concise by removing this duplication and focusing solely on the tool's functionality and usage advice.

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 (6 parameters, OHLC data), the description covers the basic purpose and performance tips but lacks details on output format (only hinted via the redundant schema snippet), error cases, or integration with sibling tools. With no output schema and rich annotations (readOnlyHint), the description is adequate but leaves gaps in fully preparing an agent for effective use, especially regarding response handling.

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 input schema has high description coverage (83%), with clear documentation for parameters like 'from', 'to', 'vs_currency', and 'jq_filter'. The description doesn't add significant semantic details beyond the schema, except implicitly reinforcing the use of 'jq_filter'. Since the schema does most of the work, the baseline score of 3 is appropriate, as the description provides minimal extra parameter insight.

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 OHLC chart (Open, High, Low, Close) of a coin within a range of timestamp based on particular coin ID.' This specifies the verb ('get'), resource ('OHLC chart'), and scope ('coin within a range of timestamp'), making it easy to understand. However, it doesn't explicitly differentiate from sibling tools like 'get_range_coins_market_chart' or 'get_range_contract_coins_market_chart', which may have overlapping functionality.

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?

The description provides some usage guidance by recommending to 'always use the `jq_filter` parameter to reduce the response size and improve performance' and noting to 'omit if you're sure you don't need the data.' This implies a performance consideration but doesn't specify when to use this tool versus alternatives (e.g., compared to other OHLC or market chart tools in the sibling list) or any prerequisites. The guidance is helpful but incomplete for tool selection.

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