Skip to main content
Glama

FiatDock

by com.fiatdock

Token price & liquidity (free)

token_price
Read-onlyIdempotent

FREE real-time price snapshot for any EVM token by contract address: USD price, 5m/1h/6h/24h change, liquidity, 24h volume, market cap/FDV and the most-liquid DEX pair (DexScreener). Or pass a major symbol (ETH/BTC) for a Coinbase spot price. Read-only, free.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainNoChain slug: base (default), ethereum, polygon, arbitrum, optimism, bsc, avalanche
tokenNoERC-20 contract address (0x…) — preferred
symbolNoMajor asset symbol (e.g. ETH, BTC) — used when no contract address is given

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
asOfYesISO 8601 time the snapshot was read
nameNoToken name
noteNoHuman-readable caveat about the snapshot, if any
chainNoChain the quoted pair trades on
queryNoThe resolved lookup this snapshot answers (echoed so an agent can confirm what was priced)
fdvUsdNoFully-diluted valuation in USD
sourceYesData source
symbolNoToken symbol
topPairNoThe most-liquid DEX pair used
txns24hNo24h buy/sell transaction counts on the top pair
priceUsdYesCurrent USD price (most-liquid pair)
recommendNoRecommended paid next step (token_safety) — present for contract-address lookups where a rug/honeypot check matters
priceChangeNoPercent price change by window
liquidityUsdNoPair liquidity in USD
marketCapUsdNoMarket cap in USD
volume24hUsdNo24h trading volume in USD

TDQS

A4.5/5.0
Behavior5/5

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

The description goes beyond annotations by detailing the exact outputs (USD price, 5m/1h/6h/24h change, liquidity, 24h volume, market cap/FDV, most-liquid DEX pair) and adds that it's free and real-time. There is no contradiction with annotations (readOnlyHint, openWorldHint, idempotentHint).

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?

The description is only two sentences, front-loaded with the primary use case and then the alternative. Every sentence is essential, with no wasted words. It is highly efficient.

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?

Given the output schema exists, the description adequately covers inputs, outputs (listed explicitly), free cost, real-time nature, and read-only behavior. No critical information is missing for a pricing snapshot tool.

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 description coverage is 100%, so the JSON schema already documents all parameters. The description adds value by explaining the use of the symbol parameter for Coinbase spot prices and stating that chain defaults to base, providing context beyond 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?

The description clearly states the tool provides a 'FREE real-time price snapshot for any EVM token by contract address' and also handles major symbols like ETH/BTC for Coinbase spot price. This specific verb+resource combination distinguishes it from siblings like token_metadata or token_safety.

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?

The description explains how to use the tool (by contract address or major symbol) and mentions it's free and read-only. However, it does not explicitly state when to use this tool over alternatives like token_metadata or provide conditions where it should not be used.

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

All FiatDock toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation4/5

Most tools are clearly separated by resource and action, but a few intentional bundles create mild selection overlap: token_report duplicates the data from token_price + token_safety, and address_intel overlaps eth_balance/usdc_balance plus safety. The descriptions explain the trade-offs well, so this is a minor rather than severe issue.

Naming Consistency4/5

Data-query tools follow a solid subject_metric pattern (token_price, usdc_balance, tx_status), while state-changing tools use verb_object (create_onramp_session, call_service). The pattern is readable and mostly consistent, but not a single uniform verb_noun convention throughout, so it falls just short of perfect.

Tool Count4/5

18 tools is above the typical 3-15 well-scoped range, but the server genuinely spans Base chain primitives, token intelligence, fiat ramps, and a marketplace. Each tool has a purpose, and the count is reasonable rather than bloated.

Completeness4/5

Core workflows are covered end-to-end: quote -> create on/off-ramp session -> order status; token price/safety/metadata/report; marketplace search/get/call; chain/tx primitives. Minor gaps exist, such as no order cancellation, no list-all-services endpoint, and no supported-country/method endpoint despite those details living in descriptions.

Resources