Skip to main content
Glama

get_verify_crypto_price

Read-only

Verify current crypto asset price via multi-source consensus. Returns attested consensus price with agreement score across independent sources (CoinGecko, Coinbase, Kraken). $0.50 USDC per call.

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

Input Schema

NameRequiredDescriptionDefault
fiatNousd
symbolYes
tolerance_pctNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and non-destructive behavior, so the safety profile is covered. The description adds genuinely useful context beyond that: the return payload (attested consensus price with an agreement score), the source list (CoinGecko, Coinbase, Kraken), and a per-call cost of $0.50 USDC, which is critical for an agent deciding whether to invoke it. It does not say what happens when sources disagree or the call fails.

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?

Three short sentences, front-loaded with purpose, then return shape, then pricing. Every sentence carries distinct information with no filler.

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

Completeness3/5

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

With no output schema, the description usefully describes the return value and cost, which is the right priority. However, for a paid verification tool with three undocumented parameters at 0% schema coverage, the definition leaves too much to inference about input formats and disagreement/failure behavior.

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

Parameters2/5

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

Schema description coverage is 0% and the description documents none of the three parameters. An agent must infer that 'symbol' is the asset ticker, that 'fiat' defaults to usd, and that 'tolerance_pct' relates to the agreement score threshold — the last is only weakly guessable from 'agreement score'. With low coverage, the description needed to compensate and does not.

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 gives a specific verb and resource ('Verify current crypto asset price') plus the mechanism ('multi-source consensus'), which clearly separates it from sibling benchmarks like get_crypto_correlation_benchmark. It stops short of explicitly naming an alternative tool, so the differentiation is implicit rather than stated.

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 context is implied by 'Verify' and by naming the three independent sources, signaling when a consensus check is warranted, but there is no explicit when-to-use/when-not-to-use guidance or comparison to other price tools such as get_copper_price_benchmark or get_cost_plus_price.

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