Skip to main content
Glama

Token price history

token_price_history
Read-only

A coin's USD price, market cap and 24h volume per day (up to 365 days back) or per hour (up to 90 days back), oldest first, by CoinGecko id (bitcoin, ethereum, usd-coin). Each point is the last sample in its day or hour, at the bucket's start. Free data from AlphaGrowth (alphagrowth.io).

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": {
      "gecko_id": "<gecko_id>"
    },
    "name": "token_price_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoHow many days back, 1 to 365 (1 to 90 for interval hour).
gecko_idYesThe coin's CoinGecko id.
intervalNoday or hour.day

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish it is a non-destructive, closed-world read. Beyond that, the description discloses the sampling rule ('last sample in its day or hour, at the bucket's start'), ordering (oldest first), and data provenance (AlphaGrowth free data), which are meaningful behavioral details not in the annotations. Rate limits and pagination are not mentioned.

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?

Front-loaded with what is returned and the day/hour lookback limits, then ordering and sampling semantics. Dense and mostly waste-free, with the trailing source attribution (alphagrowth.io) being the only marginally promotional element.

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?

For a read-only time-series tool with no output schema, the description covers the returned metrics, bucketing, ordering, and range limits well enough for an agent to call it correctly. A brief note on return container shape or response volume would make it fully complete.

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%, so the schema already documents gecko_id, interval, and days including the 365/90 relationship. The description reinforces the interval-to-max-days coupling and adds multiple gecko_id examples (bitcoin, ethereum, usd-coin) versus the schema's single example, but this is largely duplication of structured data.

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 resource and return shape: 'A coin's USD price, market cap and 24h volume per day ... or per hour', plus `oldest first` ordering and CoinGecko-id keying. It is clearly distinct from a current-price tool like token_prices by emphasizing history and bucketed series, though it never names the sibling explicitly.

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?

Usage is implied through the granularity and lookback constraints (day up to 365, hour up to 90), which tell an agent when each interval applies. There is no explicit statement of when not to use it or which sibling to prefer for current prices.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources