Skip to main content
Glama
Sign In

Agent Data Tools: Prices and DeFi

by io.github.Nutshell2000
OverviewDiscussionsAdmin

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, USDC, AERO…) or ERC-20 0x address, on Base, Ethereum, Arbitrum or Optimism, each from its deepest Uniswap v3 pool against USDC or WETH, read live from the chain, with pool, reserve and a thin-liquidity flag. Tokens without a pool are listed under unpriced instead of failing the call. Spot prices. Use to value a basket of tokens 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.

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)
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. Changed3 schema fields changed
    • changedInput schema / properties / addresses / description
      Previous value: -"Comma-separated 0x ERC-20 token addresses (1-20)"New value: +"Comma-separated 0x ERC-20 token addresses (with or instead of symbols; 1-20 tokens in all)"
    • addedInput schema / properties / symbols
      Added value: +{
+  "description": "Comma-separated tickers such as ETH,BTC,AERO (with or instead of addresses; 1-20 tokens in all)",
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "addresses"
-]
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations: names the price source (deepest Uniswap v3 pool against USDC or WETH), states that tokens without a pool land under 'unpriced' instead of failing, and lists returned fields (pool, reserve, thin-liquidity flag). It also discloses cost ($0.002/call, first 25 free, failed calls free) which explains the idempotentHint=false in practical terms — repeats cost money.

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?

Front-loads the headline capability and batch limit, then layers in source, error handling, cost, and the read-only guarantee in a tight sequence. Some density, but no sentence is filler — even the paywall line changes agent behavior.

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?

For a 3-param, no-output-schema tool, the description covers everything an agent needs: input formats, chain options, partial-failure semantics ('unpriced'), the shape of returned data, and the billing model. Nothing material is left to inference.

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 baseline is 3; the description adds a concrete example (symbols=ETH,BTC,AERO), enumerates the supported chains by name, and clarifies that symbols and addresses can be combined within the 20-token total. That is modest but real added meaning over the schema.

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?

States a specific verb+resource (USD prices for up to 20 crypto tokens in one call) with scope qualifiers: ticker or ERC-20 address, four chains, deepest Uniswap v3 pool. An agent can distinguish this batch-pricing tool from single-price siblings like price_token or crypto_price 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?

Explicitly names the use case ('value a basket of tokens or refresh a watchlist in one paid call') and the batch limit of 20, which implies when this beats a single-token call. It does not name alternative sibling tools such as price_token or crypto_price, so routing is inferred rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Agent Data Tools: Prices and DeFi toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources