Crypto, web, finance and app data tools

Crypto Price History

crypto_price_history

Daily USD price history of any token (symbol, CoinGecko id or chain:address) for up to 365 days with high, low and % change, or its exact price on a past date. Use for charts, backtests, cost basis or 'what was ETH worth on...' questions.

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": {
      "token": "<token>"
    },
    "name": "crypto_price_history"
  }
}

Input Schema

Name	Required	Description	Default
`on`	No
`days`	No
`token`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 22, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and discloses key behavior: daily granularity, maximum range of 365 days, high/low/% change output, and exact past-date pricing. It omits data source, update frequency, and any rate-limit or error behavior, but the core behavioral profile is clear.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loaded with the core capability and followed by concrete use cases. Every clause earns its place and no unnecessary detail is included.

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?

Given 3 parameters, no annotations, and an output schema that handles return values, the description covers enough for an agent to call the tool correctly. Minor gaps remain around date format and data source, but the essential calling context is present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate. It explains that 'token' accepts symbols, CoinGecko ids, or chain:address, that 'days' is limited to 365, and that 'on' returns the exact price on a past date. It does not specify the date format for 'on' or mention the default days value, but it adds substantial meaning beyond the bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: daily USD price history for any token, with explicit limits and output details. It distinguishes itself from sibling tools like crypto_candles or crypto_token_prices by focusing on historical daily data up to 365 days or exact past-date prices.

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?

It gives clear usage contexts such as charts, backtests, cost basis, and 'what was ETH worth on...' questions. However, it does not explicitly name alternative tools or state when not to use this one, leaving sibling differentiation to inference.

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

All Crypto, web, finance and app data tools 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?