Skip to main content
Glama

Token prices

token_prices
Read-only

Current USD prices of up to 30 tokens, with market cap, 24h volume and 24h change. Name each token as coingecko: (coingecko:bitcoin), : (ethereum:0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48, solana:EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v, base:0x...) or a bare CoinGecko id. Tokens without a price are listed in not_found; vault, LP and other tokens without a CoinGecko coin have a price but no market cap or volume. Free data from AlphaGrowth (alphagrowth.io).

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": {
      "tokens": "<tokens>"
    },
    "name": "token_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokensYesComma-separated tokens: coingecko:<id>, <chain>:<address> or a CoinGecko id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/destructive hints, yet the description adds real value beyond them: a hard 30-token limit, the existence of a not_found list, and the caveat that vault/LP tokens return a price without market cap or volume. The upstream data source is also disclosed. Missing only error-handling or rate-limit behavior.

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-loads what is returned, then the input formats, then edge cases — a logical order with no filler sentences. Slightly heavy on inline examples (three chain formats) that duplicate the schema examples, but nothing is wasted.

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?

With no output schema, the description carries the return-shape burden and does so: it names the fields returned, the not_found bucket, and the partial-data case for non-CoinGecko tokens. For a one-parameter read tool, an agent has everything needed to call it and interpret results.

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 parameter's description already covers comma-separated coingecko:/chain:address/bare-id formats with examples. The description largely restates that in prose with more examples rather than adding new syntax rules, so the high-coverage baseline of 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?

States a specific verb and resource ('Current USD prices of up to 30 tokens') plus the returned fields (market cap, 24h volume, 24h change). 'Current' implicitly contrasts with the sibling token_price_history, but that sibling is never named, so the differentiation is left to inference.

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 is implied by 'Current' and the 30-token cap, but there is no explicit when-to-use statement and no named alternative for historical lookups. The not_found behavior gives partial operational guidance but not task routing.

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