Skip to main content
Glama

Crypto Intraday Prices

GetCryptoIntradayPrices
Read-only

Get price candles within the day 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, around the clock. interval is any whole minutes from 1min (default) to 240min, or 1hour to 4hour, counted from midnight UTC. Defaults to the last 7 days (30 for hourly); startDate and endDate set another, back to the coin's first trade. A period without trades has no candle. A cut answer names the next endTime. Candles are added some minutes after they end; the answer says how far they reach. Plus reads a candle 15 minutes after it ends, Free gets an upgrade note. Prices and volume are one exchange's. GetCryptoPrices has daily candles, GetCryptoQuote the latest price.

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": "GetCryptoIntradayPrices"
  }
}

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)
endTimeNoReturn only candles that start before this RFC 3339 time; replaces endDate
intervalNoCandle size: whole minutes from 1min to 240min (e.g. 5min, 15min), or 1hour to 4hour (default: 1min)1min
startDateNoFirst UTC day in YYYY-MM-DD format (default: 7 days before the end, 30 for hourly intervals)
maxResultsNoMaximum candles to return, newest first (default: 60, max: 500)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover the read-only, non-destructive, non-open-world profile, and the description adds real behavior beyond that: candles land some minutes after they end, the response reports data freshness, gaps in trading produce no candle, and a truncated answer names the next endTime for continuation. It also discloses that prices and volume come from a single exchange. Not a 5 only because the plan-tier and freshness notes are stated tersely enough that exact response fields remain implicit.

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?

Purpose and asset-class disambiguation are front-loaded, and nearly every sentence carries distinct information. The telegraphic, run-on phrasing ('Plus reads a candle 15 minutes after it ends, Free gets an upgrade note') costs some readability but not much length.

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?

For a six-parameter read tool with no output schema, the description covers units, asset class, freshness, default windows, gap behavior, truncation/continuation, plan limits, and sibling routing. An agent has everything needed to call it and interpret a partial 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 the baseline is 3, and the description goes beyond it: it anchors interval counting to midnight UTC, spells out the 1min–240min and 1hour–4hour ranges together with the varying default window (7 days, 30 for hourly), and clarifies that startDate/endDate reach back to the coin's first trade. It still leaves the interaction between endTime and maxResults largely to the 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?

States a specific verb and resource ('Get price candles within the day') plus the returned fields (open, high, low, close, volume) and explicitly disambiguates the asset class ('ONE crypto COIN (not a stock: BTC here is Bitcoin)'). It also names the two nearest siblings and what each returns, so an agent can pick this tool 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: 'GetCryptoPrices has daily candles, GetCryptoQuote the latest price,' which gives the condition that selects this tool over those alternatives. It also gives plan-tier conditions ('Plus reads a candle 15 minutes after it ends, Free gets an upgrade note'), so the agent knows when the response may be incomplete.

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.