Skip to main content
Glama

Crypto price and token price: USD price of a token from Uniswap v3 pools

price_token
Read-only

Token price in USD for a crypto token by symbol, coin name or CoinGecko id from a built-in list of main tokens (ETH, BTC, USDC, AERO, ARB, OP, LINK, PEPE…) or any ERC-20 0x address on Base, Ethereum, Arbitrum or Optimism, from the deepest Uniswap v3 pool against USDC or WETH, read live. Returns pool, fee tier, reserve and a thin-liquidity flag. Spot price; no pool is 422, uncharged. Use to value a token or check a quote before a swap or payment. Example: symbol=ETH. Price $0.002/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "price_token"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoNetwork: base (default), eth, arb, op or polygon
symbolNoTicker such as ETH, BTC, USDC, AERO, ARB, OP or LINK. Send symbol or address, one of the two (ETH and BTC mean the wrapped tokens; an HTTP call with no input at all answers for BTC)
addressNo0x ERC-20 token contract address, sent instead of symbol (when both are sent, the address is priced). WETH on Base is 0x4200000000000000000000000000000000000006

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / chain / description
      Previous value: -"Network: base (default), eth, arb or op"New value: +"Network: base (default), eth, arb, op or polygon"
    • changedInput schema / properties / chain / enum
      Previous value: -[
      -  "base",
      -  "eth",
      -  "arb",
      -  "op"
      -]New value: +[
      +  "base",
      +  "eth",
      +  "arb",
      +  "op",
      +  "polygon"
      +]
  2. Changed2 schema fields changed
    • changedInput schema / properties / address / description
      Previous value: -"0x ERC-20 token contract address (instead of symbol)"New value: +"0x ERC-20 token contract address, sent instead of symbol (when both are sent, the address is priced). WETH on Base is 0x4200000000000000000000000000000000000006"
    • changedInput schema / properties / symbol / description
      Previous value: -"Ticker such as ETH, BTC, USDC, AERO, ARB, OP or LINK (instead of address; ETH and BTC mean the wrapped tokens; an HTTP call with no input at all answers for BTC)"New value: +"Ticker such as ETH, BTC, USDC, AERO, ARB, OP or LINK. Send symbol or address, one of the two (ETH and BTC mean the wrapped tokens; an HTTP call with no input at all answers for BTC)"
  3. Changed1 schema field changed
    • changedInput schema / properties / symbol / description
      Previous value: -"Ticker such as ETH, BTC, USDC, AERO, ARB, OP or LINK (instead of address; ETH and BTC mean the wrapped tokens)"New value: +"Ticker such as ETH, BTC, USDC, AERO, ARB, OP or LINK (instead of address; ETH and BTC mean the wrapped tokens; an HTTP call with no input at all answers for BTC)"
  4. Changed3 schema fields changed
    • changedInput schema / properties / address / description
      Previous value: -"0x ERC-20 token contract address"New value: +"0x ERC-20 token contract address (instead of symbol)"
    • addedInput schema / properties / symbol
      Added value: +{
      +  "description": "Ticker such as ETH, BTC, USDC, AERO, ARB, OP or LINK (instead of address; ETH and BTC mean the wrapped tokens)",
      +  "type": "string"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "address"
      -]
  5. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true and idempotentHint=false, so the safety profile is covered. The description still adds real value beyond them: the returned fields (pool, fee tier, reserve, thin-liquidity flag), the 422-and-uncharged behavior when no pool exists, and the per-call cost with 25 free calls and free failures. The 'each call is charged, so repeats are not free' line usefully explains the non-idempotent hint.

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?

The most decision-relevant facts (what it prices, from where, on which chains) are front-loaded, and the pricing/error notes come last. It is a dense run-on paragraph with some overlap between 'Spot price' and 'Reads or computes only and changes nothing', but almost every clause carries information.

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 returned fields and the no-pool error case, and it covers cost and read-only semantics. The only gap is the unmentioned polygon chain, which the schema supplies.

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%, so the baseline is 3. The description does add meaning the schema lacks, notably that symbol also accepts a coin name or CoinGecko id, but it lists only Base, Ethereum, Arbitrum and Optimism while the chain enum also includes polygon, leaving a small inconsistency an agent must resolve from the schema.

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 states a specific verb and resource ('Token price in USD for a crypto token') and pins down the data source (deepest Uniswap v3 pool against USDC or WETH, read live) plus accepted identifiers (symbol, coin name, CoinGecko id, or 0x address). It never names or contrasts a sibling such as crypto_price, price_tokens, or btc_price, so an agent cannot rule out overlap from the text alone.

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

Usage Guidelines4/5

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

'Use to value a token or check a quote before a swap or payment' gives a clear positive use case, reinforced by the 'Example: symbol=ETH' call pattern. There are no when-not-to-use conditions and no named alternatives, which keeps it short of a 5.

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.