Skip to main content
Glama

Crypto Quote

GetCryptoQuote
Read-only

Get the latest US dollar price of crypto COINS (not stocks: BTC here is Bitcoin, not a stock ticker), up to 25 a call: last trade price and its UTC time, the 24-hour change, and the 24-hour volume, high and low. Prices and volume are one exchange's, not the whole market's; there is no market cap. A quiet coin shows an old last-trade time; that is its real last trade. Pro reads real time, Plus 15 minutes delayed, Free gets an upgrade note (daily candles are in GetCryptoPrices). ListCryptoAssets lists 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": {
      "symbols": "<symbols>"
    },
    "name": "GetCryptoQuote"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolsYesCoin symbols (max 25), e.g. BTC, ETH, SOL; BTC/USD and BTC-USD also work

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?

Beyond the readOnly/non-destructive/non-open-world annotations, it discloses that prices are from a single exchange rather than the whole market, that there is no market cap, and that stale last-trade times are real rather than errors. It also documents entitlement behavior: real time on Pro, 15-minute delay on Plus, an upgrade note on Free — a genuine behavioral caveat annotations cannot express. The only gap is nothing about error behavior for invalid symbols.

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 action and the stock-vs-coin disambiguation in the first sentence, with caveats and sibling routing trailing after. It is dense and long for one parameter, but each clause (exchange scope, staleness, tier delays, sibling pointers) carries distinct information rather than 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, so the description carries the return-value burden and does so by naming every field returned, plus the entitlement difference in what data you actually get. For a one-parameter read tool, an agent has everything needed to call it and interpret the result correctly.

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 schema already documents the single symbols array and its alternate formats (BTC/USD, BTC-USD). The description reinforces the meaningful constraint — max 25 per call — and frames the parameter as coin symbols rather than stock tickers, adding interpretation beyond the field description.

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 the latest US dollar price of crypto COINS") and immediately scopes it against a common confusion by declaring BTC here is Bitcoin, not a stock ticker. It also enumerates exactly what is returned (last trade price + UTC time, 24h change, 24h volume/high/low), so an agent can distinguish it from quote tools for equities.

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 between siblings: daily candles belong in GetCryptoPrices, symbol discovery belongs in ListCryptoAssets. It also states the batching limit (up to 25 a call) and warns that quiet coins show an old last-trade time rather than implying missing data.

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.