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

Name	Required	Description
`chain`	No	Chain slug: base (default), ethereum, polygon, arbitrum, optimism, bsc, avalanche
`token`	No	ERC-20 contract address (0x…) — preferred
`symbol`	No	Major asset symbol (e.g. ETH, BTC) — used when no contract address is given

Output Schema

TableJSON Schema

Name	Required	Description
`asOf`	Yes	ISO 8601 time the snapshot was read
`name`	No	Token name
`note`	No	Human-readable caveat about the snapshot, if any
`chain`	No	Chain the quoted pair trades on
`query`	No	The resolved lookup this snapshot answers (echoed so an agent can confirm what was priced)
`fdvUsd`	No	Fully-diluted valuation in USD
`source`	Yes	Data source
`symbol`	No	Token symbol
`topPair`	No	The most-liquid DEX pair used
`txns24h`	No	24h buy/sell transaction counts on the top pair
`priceUsd`	Yes	Current USD price (most-liquid pair)
`recommend`	No	Recommended paid next step (token_safety) — present for contract-address lookups where a rug/honeypot check matters
`priceChange`	No	Percent price change by window
`liquidityUsd`	No	Pair liquidity in USD
`marketCapUsd`	No	Market cap in USD
`volume24hUsd`	No	24h trading volume in USD

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedJul 30, 2026

addedOutput schema / properties / recommend / properties / alternatives

Added value: +{
+  "description": "Higher-value paid next steps beyond the primary token_safety — the token_report bundle and an address_intel screen of the contract (ADR-0063)",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "call": {
+        "additionalProperties": false,
+        "properties": {
+          "args": {
+            "additionalProperties": false,
+            "properties": {
+              "address": {
+                "type": "string"
+              },
+              "chain": {
+                "type": "string"
+              },
+              "token": {
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "mcpTool": {
+            "type": "string"
+          },
+          "rest": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "mcpTool",
+          "rest",
+          "args"
+        ],
+        "type": "object"
+      },
+      "priceUsd": {
+        "type": "number"
+      },
+      "reason": {
+        "type": "string"
+      },
+      "tool": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "tool",
+      "priceUsd",
+      "reason",
+      "call"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / recommend / properties / call / properties / args / properties / address
```
Added value: +{
+  "type": "string"
+}
```

Changed1 schema field changedJul 29, 2026

addedOutput schema / properties / txns24h

Added value: +{
+  "additionalProperties": false,
+  "description": "24h buy/sell transaction counts on the top pair",
+  "properties": {
+    "buys": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "sells": {
+      "type": [
+        "number",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedJul 29, 2026

addedOutput schema / properties / query

Added value: +{
+  "additionalProperties": {},
+  "description": "The resolved lookup this snapshot answers (echoed so an agent can confirm what was priced)",
+  "type": "object"
+}

Changed2 schema fields changedJul 26, 2026

addedOutput schema / properties / recommend / properties / mcpTool

Added value: +{
+  "description": "For a listing whose endpoint is an MCP SERVER: the tool call_service invokes there. When present, args are wrapped in a JSON-RPC tools/call envelope",
+  "type": "string"
+}

addedOutput schema / properties / recommend / properties / x402PriceUsd

Added value: +{
+  "description": "REAL per-call x402 price for a first-party listing whose endpoint sits behind FiatDock's own paywall. priceUsd is 0 there only because such listings are not gateway-routed — budget from THIS field when present",
+  "type": "number"
+}

Changed1 schema field changedJul 5, 2026

addedOutput schema / properties / recommend

Added value: +{
+  "additionalProperties": false,
+  "description": "Recommended paid next step (token_safety) — present for contract-address lookups where a rug/honeypot check matters",
+  "properties": {
+    "call": {
+      "additionalProperties": false,
+      "description": "The exact next call to make",
+      "properties": {
+        "args": {
+          "additionalProperties": false,
+          "properties": {
+            "chain": {
+              "type": "string"
+            },
+            "token": {
+              "type": "string"
+            }
+          },
+          "type": "object"
+        },
+        "mcpTool": {
+          "type": "string"
+        },
+        "rest": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "mcpTool",
+        "rest",
+        "args"
+      ],
+      "type": "object"
+    },
+    "priceUsd": {
+      "description": "Its price in USD (x402)",
+      "type": "number"
+    },
+    "reason": {
+      "description": "Why to run it before trading",
+      "type": "string"
+    },
+    "tool": {
+      "description": "Suggested next tool (token_safety)",
+      "type": "string"
+    }
+  },
+  "required": [
+    "tool",
+    "priceUsd",
+    "reason",
+    "call"
+  ],
+  "type": "object"
+}

Changed1 schema field changedJul 5, 2026
- addedOutput schema / properties / note / description
```
Added value: +"Human-readable caveat about the snapshot, if any"
```
AddedJun 22, 2026

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 tools Inspect

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.