Skip to main content
Glama

Crypto price

crypto_price
Read-only

Get current price, market cap, volume, and 24h/7d change for any cryptocurrency. Supports search by name, symbol, or CoinGecko ID. Costs $0.001 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": {
      "query": "<query>"
    },
    "name": "crypto_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesCoin name, symbol, or ID (e.g. 'bitcoin', 'ETH', 'solana')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the bar is lower; the description still adds a genuinely useful, non-annotation behavior: it costs $0.001 USDC per call, which affects whether an agent should batch or avoid it. It also enumerates the returned fields, which matters since no output schema exists. It does not say what happens when the query resolves to multiple coins or no coin.

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 what is returned, then input flexibility, then cost. No filler; the cost sentence earns its place by informing call budgeting.

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?

With no output schema, the description correctly compensates by naming the return fields (price, market cap, volume, 24h/7d change), and it discloses pricing. Minor gap: no statement about behavior on ambiguous or unknown queries, which is plausible for a free-text lookup.

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

Parameters3/5

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

Schema coverage is 100% and the single query parameter already documents accepted forms (name, symbol, ID) with examples. The description's 'supports search by name, symbol, or CoinGecko ID' restates the schema rather than extending it with format or ambiguity-resolution rules. Baseline 3 applies.

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?

Specific verb+resource: returns price, market cap, volume, and 24h/7d change for a cryptocurrency. However, it never distinguishes itself from the sibling token_price, which an agent will naturally compare against before choosing.

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

Usage Guidelines2/5

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

It says it works for 'any cryptocurrency' but gives no when-to-use guidance, no exclusions, and no mention of when token_price or pair_data would be the better pick. The agent is left to infer selection from the field list alone.

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