AIsa Finance

Coin Historical Chart Data within Time Range by Token Address

get_coingecko_token_market_chart_range

Read-onlyIdempotent

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

Published reference price: $0.008 USD per successful request. Declared unit rate: $0 USD per provider_credit. Account-specific pricing and final settlement may differ.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "contract_address": "<contract_address>",
      "id": "<id>",
      "from": "<from>",
      "to": "<to>",
      "vs_currency": "<vs_currency>"
    },
    "name": "get_coingecko_token_market_chart_range"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Asset platform ID. *refers to [`/asset_platforms`](/reference/asset-platforms-list).	ethereum
`to`	Yes	Ending date in ISO date string (`YYYY-MM-DD` or `YYYY-MM-DDTHH:MM`) or UNIX timestamp. Use ISO date string for best compatibility.	2025-12-31
`from`	Yes	Starting date in ISO date string (`YYYY-MM-DD` or `YYYY-MM-DDTHH:MM`) or UNIX timestamp. Use ISO date string for best compatibility.	2025-12-22
`interval`	No	Data interval, leave empty for auto granularity.
`precision`	No	Decimal place for currency price value.
`vs_currency`	Yes	Target currency of market data. *refers to [`/simple/supported_vs_currencies`](/reference/simple-supported-currencies).	usd
`contract_address`	Yes	The contract address of token.	0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed20 schema fields changedOct 15, 2026

addedInput schema / properties / contract_address / default

Added value: +"0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"

changedInput schema / properties / contract_address / description

Previous value: -"Token contract address."New value: +"The contract address of token."

removedInput schema / properties / contract_address / example

Removed value: -"0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"

addedInput schema / properties / from / default
```
Added value: +"2025-12-22"
```

changedInput schema / properties / from / description

Previous value: -"Start UNIX timestamp (seconds)."New value: +"Starting date in ISO date string (`YYYY-MM-DD` or `YYYY-MM-DDTHH:MM`) or UNIX timestamp. \n**Use ISO date string for best compatibility.**"

removedInput schema / properties / from / example
```
Removed value: -1751328000
```

changedInput schema / properties / from / type

Previous value: -"integer"New value: +"string"

addedInput schema / properties / id / default
```
Added value: +"ethereum"
```

changedInput schema / properties / id / description

Previous value: -"Asset platform ID (e.g., `ethereum`)."New value: +"Asset platform ID. \n*refers to [`/asset_platforms`](/reference/asset-platforms-list)."

removedInput schema / properties / id / example
```
Removed value: -"ethereum"
```

addedInput schema / properties / interval

Added value: +{
+  "description": "Data interval, leave empty for auto granularity.",
+  "enum": [
+    "1m",
+    "5m",
+    "hourly",
+    "daily"
+  ],
+  "type": "string"
+}

changedInput schema / properties / precision / description

Previous value: -"`full` or a value from `0` to `18` to specify decimal places for currency price values."New value: +"Decimal place for currency price value."

addedInput schema / properties / precision / enum

Added value: +[
+  "full",
+  "0",
+  "1",
+  "2",
+  "3",
+  "4",
+  "5",
+  "6",
+  "7",
+  "8",
+  "9",
+  "10",
+  "11",
+  "12",
+  "13",
+  "14",
+  "15",
+  "16",
+  "17",
+  "18"
+]

removedInput schema / properties / precision / example
```
Removed value: -"2"
```
addedInput schema / properties / to / default
```
Added value: +"2025-12-31"
```

changedInput schema / properties / to / description

Previous value: -"End UNIX timestamp (seconds)."New value: +"Ending date in ISO date string (`YYYY-MM-DD` or `YYYY-MM-DDTHH:MM`) or UNIX timestamp. \n**Use ISO date string for best compatibility.**"

removedInput schema / properties / to / example
```
Removed value: -1751414400
```

changedInput schema / properties / to / type

Previous value: -"integer"New value: +"string"

changedInput schema / properties / vs_currency / description

Previous value: -"Target currency for price (e.g., `usd`, `eur`, `btc`). See `/simple/supported_vs_currencies`."New value: +"Target currency of market data. \n*refers to [`/simple/supported_vs_currencies`](/reference/simple-supported-currencies)."

changedInput schema / required

Previous value: -[
-  "id",
-  "contract_address",
-  "vs_currency",
-  "from",
-  "to"
-]New value: +[
+  "contract_address",
+  "id",
+  "from",
+  "to",
+  "vs_currency"
+]

Changed5 schema fields changedSep 18, 2026
- addedInput schema / properties / contract_address / example
```
Added value: +"0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"
```
- addedInput schema / properties / from / example
```
Added value: +1751328000
```
- addedInput schema / properties / id / example
```
Added value: +"ethereum"
```
- addedInput schema / properties / precision / example
```
Added value: +"2"
```
- addedInput schema / properties / to / example
```
Added value: +1751414400
```
First observedSep 15, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety is covered, but the description adds no behavioral context beyond that — no rate limits, no note that it is a paid endpoint beyond the injected pricing block, and no granularity/auto-interval behavior. It also says the range is 'in UNIX' while the schema instructs ISO date strings for best compatibility, which adds confusion rather than clarity.

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 core purpose is front-loaded in a single dense sentence, but that sentence is over-long and contains the misleading 'in UNIX' claim. The appended pricing boilerplate consumes roughly half the text without helping an agent select or invoke the tool.

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?

With an output schema and full annotation coverage, the description need not explain return values, and the inputs are documented in the schema. What is missing is the differentiation and usage context that would let an agent choose this tool over its range/market-chart siblings.

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%, with defaults, enums and per-parameter docs already present, so the baseline is 3. The description only restates the high-level output dimensions (price, market cap, 24hr volume) and the platform/contract-address inputs without adding format, interval, or precision semantics beyond the schema.

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 names a specific verb and resource ('get the historical chart data within certain time range... along with price, market cap and 24hr volume') and scopes it to a token contract address on an asset platform. It does not, however, distinguish itself from near-identical siblings such as get_coingecko_token_market_chart or get_coingecko_coins_id_market_chart_range, so the agent must guess which range/market-chart variant to call.

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 explicit when-to-use guidance and no alternatives named, despite three closely related market-chart siblings in the list. The only usage signal is the implicit 'based on asset platform and particular token contract address', which is a scope statement, not routing guidance.

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

All AIsa Finance tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?