Skip to main content
Glama

Uniswap v3 pool stats on Base (x402)

Uniswap v3 pool liquidity and recent volume on Base: token symbols and decimals, fee tier, in-range liquidity, price bot

uniswap_pool_stats
Read-onlyIdempotent

Uniswap v3 pool liquidity and recent volume on Base: token symbols and decimals, fee tier, in-range liquidity, price both ways, plus swap count and traded volume over about the last hour, read from the pool and its Swap logs (pool=0x..., default WETH/USDC). For trading, liquidity-provision and risk agents. Pay per call $0.01 USDC on Base via x402.

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": "uniswap_pool_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
poolNoUniswap v3 pool address on Base, 0x..., default WETH/USDC
x_paymentNosigned x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint), so the description's added value is in disclosing data provenance (read from the pool contract and its Swap logs), the ~1 hour window, and the pricing model. The $0.01 USDC per-call x402 charge and the first-call payment handshake are exactly the kind of non-obvious behavior an agent needs before invoking.

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 output fields are front-loaded in one dense sentence, followed by audience and payment terms — no filler sentences. It is long but every clause carries information; the only minor waste is repeating the title's field list.

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 carries the burden of describing returns and does so by enumerating the returned fields and their time window. It leaves unit conventions (e.g. raw vs. human decimals for volume, price orientation) and error behavior unstated, which keeps it short of a 5.

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 description coverage is 100%, so both `pool` and `x_payment` are already documented, including the 0x... format and the WETH/USDC default. The description restates the pool default and adds only that payment is required, which is marginal value beyond the schema; baseline 3 applies.

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?

States a specific verb and resource: reads Uniswap v3 pool liquidity and recent volume on Base, and enumerates the returned fields (token symbols/decimals, fee tier, in-range liquidity, price both ways, swap count, volume over ~last hour). That clearly distinguishes it from a pure price tool or a pure swaps tool, though it never names a sibling alternative explicitly.

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?

'For trading, liquidity-provision and risk agents' implies the intended use case but gives no explicit when-to-use vs. when-to-use-another-tool rule and no exclusions. An agent must infer that this is the aggregate/snapshot tool rather than the raw-swaps or single-price tools.

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.

Resources