Skip to main content
Glama

Crypto Daily Prices

GetCryptoPrices
Read-only

Get daily price candles for ONE crypto COIN (not a stock: BTC here is Bitcoin), newest first: open, high, low, close, volume in the coin's own units and trades, in US dollars. A day runs midnight to midnight UTC; a day without trades has no candle. History goes back to the coin's first trade on the exchange (BTC: 2013). Prices and volume are one exchange's, not the whole market's. Plus and Pro also get the day in progress; Free gets a day 4 hours after it ends. GetCryptoQuote has the latest price, GetCryptoIntradayPrices candles within the day, ListCryptoAssets the symbols.

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": {
      "symbol": "<symbol>"
    },
    "name": "GetCryptoPrices"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesCoin symbol, e.g. BTC; BTC/USD and BTC-USD also work
endDateNoLast UTC day in YYYY-MM-DD format (default: today)
startDateNoFirst UTC day in YYYY-MM-DD format (default: the coin's first trade)
maxResultsNoMaximum days to return, newest first (default: 60, max: 500)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare a safe read, but the description adds substantial non-obvious behavior: day boundaries are midnight-to-midnight UTC, empty days produce no candle, history extends to the coin's first trade (BTC: 2013), prices reflect a single exchange rather than the whole market, and tier gating determines whether today's in-progress day appears (Plus/Pro immediately, Free 4 hours after close). None of that is recoverable from the annotations or schema.

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 the core verb and scope, and every sentence carries information. However, it is a dense run-on paragraph mixing return format, time semantics, data provenance, and tier limits, which would scan better as separated clauses despite there being no filler.

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

Completeness5/5

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

There is no output schema, and the description compensates by naming the returned candle fields and ordering. Combined with provenance, history depth, UTC day rules, and subscription-tier effects, an agent has everything needed to call it and interpret the result.

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 100%, so baseline is 3, but the description adds genuine meaning: symbol is a coin not a stock and accepts BTC as Bitcoin, and 'newest first' frames how maxResults and the date window interact. It does not restate the accepted symbol formats or the 500 max, which the schema already covers, so it stops short of a 5.

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?

States a specific verb and resource ('Get daily price candles for ONE crypto COIN') and immediately scopes it against a common confusion ('not a stock: BTC here is Bitcoin'), then enumerates the returned fields (open, high, low, close, volume, trades). An agent can distinguish it from GetCryptoQuote and GetCryptoIntradayPrices without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent to alternatives with their selecting conditions: 'GetCryptoQuote has the latest price, GetCryptoIntradayPrices candles within the day, ListCryptoAssets the symbols.' It also states the boundary condition for this tool via the candle granularity and the day-without-trades case.

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.