Skip to main content
Glama

Uniswap v3 recent swaps on Base (x402)

Recent swaps of a Uniswap v3 pool on Base, newest first: estimated time, buy or sell direction, token amounts, execution

uniswap_recent_swaps
Read-onlyIdempotent

Recent swaps of a Uniswap v3 pool on Base, newest first: estimated time, buy or sell direction, token amounts, execution price and transaction hash for up to 50 swaps (pool=0x..., count=20; default WETH/USDC). The raw trade tape for trading and market-making agents, read from on-chain Swap logs. Pay per call $0.02 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_recent_swaps"
  }
}

Input Schema

NameRequiredDescriptionDefault
poolNoUniswap v3 pool address on Base, 0x..., default WETH/USDC
countNohow many swaps, 1-50, default 20
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

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, open-world. The description adds genuinely non-structured behavior: the data source ('read from on-chain Swap logs'), the 50-item hard cap, and the $0.02 USDC x402 pay-per-call model. It stops short of describing failure modes (invalid pool address, over-cap count) or what a missing-payment response looks like.

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?

Three tight sentences: capability and return shape first, audience/source next, pricing last. No filler, no repetition of the title, and the most decision-relevant facts are front-loaded.

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?

No output schema exists, yet the description enumerates the returned fields (time, buy/sell direction, amounts, execution price, tx hash) and the cap, and the payment gate is explained jointly with the schema. An agent has everything needed to call it and interpret the result.

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 coverage is 100%, so pool, count, and x_payment are already fully documented, including the default WETH/USDC pool and the first-call payment handshake. The description's inline example (pool=0x..., count=20) restates schema facts rather than adding new meaning, so the baseline 3 is correct.

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 and resource ('Recent swaps of a Uniswap v3 pool on Base'), names the ordering ('newest first'), enumerates the returned fields, and gives a concrete invocation example. The phrase 'raw trade tape' implicitly separates it from aggregate siblings like uniswap_pool_stats and pool_candles, so an agent can select it without opening a 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?

Gives a clear use-case context ('for trading and market-making agents') that tells an agent when this tool is the right pick, but never names an alternative or an exclusion (e.g., when to prefer pool stats or candles instead). Clear context without exclusions lands at 4.

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