Skip to main content
Glama

AIsa Finance

by one.aisa
OverviewDiscussionsAdmin

Coin Historical Chart Data by Token Address

get_coingecko_token_market_chart
Read-onlyIdempotent

This endpoint allows you to get the historical chart data including time in UNIX, 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesAsset platform ID. *refers to [`/asset_platforms`](/reference/asset-platforms-list).ethereum
daysYesData up to number of days ago. You may use any integer or `max` for number of days.1
intervalNoData interval, leave empty for auto granularity.
precisionNoDecimal place for currency price value.
vs_currencyYesTarget currency of market data. *refers to [`/simple/supported_vs_currencies`](/reference/simple-supported-currencies).usd
contract_addressYesThe contract address of token.0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changed
    • addedInput schema / properties / contract_address / default
      Added value: +"0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"
    • changedInput schema / properties / contract_address / description
      Previous value: -"Contract address."New value: +"The contract address of token."
    • addedInput schema / properties / days / default
      Added value: +"1"
    • changedInput schema / properties / days / description
      Previous value: -"Data up to N days ago. Accepts `1`, `7`, `14`, `30`, `90`, `180`, `365`, or `max`."New value: +"Data up to number of days ago. \nYou may use any integer or `max` for number of days."
    • removedInput schema / properties / days / example
      Removed value: -"7"
    • addedInput schema / properties / id / default
      Added value: +"ethereum"
    • changedInput schema / properties / id / description
      Previous value: -"Platform ID."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"
    • 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",
-  "days"
-]New value: +[
+  "contract_address",
+  "id",
+  "days",
+  "vs_currency"
+]
  2. Changed3 schema fields changed
    • addedInput schema / properties / days / example
      Added value: +"7"
    • addedInput schema / properties / id / example
      Added value: +"ethereum"
    • addedInput schema / properties / precision / example
      Added value: +"2"
  3. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds the returned data shape (UNIX time, price, market cap, 24hr volume) and a per-request price, but says nothing about rate limits, pagination, or historical depth limits ('max'). With annotations doing the heavy lifting, this is an adequate 3.

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 functional sentence is single and front-loaded, and the injected pricing block is clearly delimited boilerplate rather than prose. Slight bloat from the pricing/metadata block, but the core content is tight.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has rich annotations, full schema coverage and an output schema, so return values and safety need not be explained. The description is complete enough for correct invocation, though it omits sibling routing and any note on granularity behavior (interval vs days interaction).

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% and two parameters carry enums, so the schema already documents id, days, interval, precision, vs_currency and contract_address thoroughly. The description adds no parameter-level meaning beyond echoing 'asset platform and particular token contract address'. Baseline 3 applies when the schema does the 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 states a specific verb (get) and resource (historical chart data) and names the disambiguating scoping dimension: 'based on asset platform and particular token contract address'. This implicitly separates it from the coin-id based siblings, but it never names get_coingecko_coins_id_market_chart or get_coingecko_token_market_chart_range explicitly, so differentiation requires inference.

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 when-to-use guidance, no when-not-to-use, and no named alternative, despite several closely related siblings (get_coingecko_coins_id_market_chart, get_coingecko_token_market_chart_range) that an agent must choose between. The agent is left to infer the choice entirely from the resource wording.

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

All AIsa Finance toolsInspect
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