Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Crypto prices in USD for up to 20 tokens in one call: get USD prices for several crypto tokens or coins in one call

price_tokens
Read-only

USD prices for up to 20 crypto tokens in one call, by ticker (ETH, BTC, LINK, AERO…) or ERC-20 0x address, on Base, Ethereum, Arbitrum and Optimism, each from its deepest Uniswap v3 pool against USDC or WETH, read live, with pool, reserve and a thin-liquidity flag. With no chain named each ticker is priced on the network that lists it. Tokens without a pool are listed as unpriced. Use to value a basket or refresh a watchlist in one paid call. Example: symbols=ETH,BTC,AERO. 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_tokens"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoNetwork: base (default), eth, arb or op
symbolsNoComma-separated tickers such as ETH,BTC,AERO (with or instead of addresses; 1-20 tokens in all; an HTTP call with no input at all answers for BTC and ETH)
addressesNoComma-separated 0x ERC-20 token addresses (with or instead of symbols; 1-20 tokens in all)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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 nonetheless earns credit for genuinely new behavioral context: the per-call price ($0.002), payment paths (x402 USDC or card key), 25 free calls, failed calls free, and the explicit explanation that repeats are not free — which justifies the non-idempotent hint. The thin-liquidity flag and the 'unpriced' fallback are also disclosed. It does not describe response shape beyond those fields or any rate limits, keeping it at a solid 3 rather than higher.

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 first sentence front-loads the core capability and constraints, and the pricing/payment facts are consolidated at the end. The opening sentence is dense with many appended clauses (all four chains, pool source, reserve, thin-liquidity flag), which makes it heavier than necessary but every element carries information.

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, and the description compensates by naming what comes back (pool, reserve, thin-liquidity flag) and how failures manifest (tokens without a pool listed as unpriced). Cost, payment, default-chain behavior and the 20-token limit are all covered, leaving nothing an agent needs before calling it.

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 baseline would be 3, but the description adds real meaning: symbols accept tickers 'with or instead of' addresses, the 1-20 combined cap, and the notable default behavior that an unnamed chain prices each ticker on the network that lists it. That last point adds semantics the chain enum's '(default)' note does not fully convey, though it sits in mild tension with the schema's 'base (default)' wording.

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?

The description states a specific verb and resource (USD prices for crypto tokens), the exact batch capacity (up to 20 in one call), the accepted identifiers (ticker or ERC-20 0x address), the supported chains, and the pricing source (deepest Uniswap v3 pool against USDC or WETH). This is enough to separate it from single-token siblings like price_token without opening any schema.

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 basket or refresh a watchlist in one paid call' gives a clear when-to-use context, and the 20-token cap implies batching rather than single lookups. However, no sibling is named explicitly (e.g. 'for one token use price_token'), and there is no stated when-not-to-use condition, so the routing is implied rather than explicit.

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.