Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

New pools, new token pairs: Uniswap and Aerodrome

dex_new_pools
Read-only

Newest liquidity pools on Uniswap v3, Uniswap v2 and (on Base) Aerodrome, read live from the factories' PoolCreated and PairCreated events on Base, Ethereum, Arbitrum, Optimism or Polygon: pool address, both tokens with symbol and decimals, fee tier or stable flag, block, transaction and approximate age, newest first. Use to spot new token listings, watch pool launches or feed a new-pair screener; check token_report before trading. Example: chain=base. Price $0.01/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.

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

Input Schema

NameRequiredDescriptionDefault
dexNoall (default), uniswap-v3, uniswap-v2 or aerodrome (Base only)
chainNobase (default), ethereum, arbitrum, optimism or polygon
limitNoMost pools to return, 1 to 30 (default 20)
blocksNoHow many recent blocks to scan, 100 to 20000 (default 3000: about 10 hours on Ethereum); on Base, which makes a block every 0.2 s, ten times that (default 30000, about 100 minutes, up to 200000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld/non-destructive, and the description still adds substantive context: live event-derived data, newest-first ordering, per-call pricing ($0.01, first 25 free, failed calls free), and the explicit warning that repeats are charged — consistent with idempotentHint=false. None of that is inferable from the structured fields.

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?

Purpose, coverage, data source and return fields are packed into the front-loaded first sentence/clause before usage and pricing. Every remaining clause (use cases, token_report warning, example, pricing, read-only note) carries distinct information, with no filler.

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?

With no output schema, the description compensates by enumerating the returned fields and their ordering. Chain coverage, event source, cost model, and the read-only/no-mutation guarantee are all stated, so an agent can call it correctly and interpret the result without extra lookups.

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%, with each of dex, chain, limit and blocks already documented, including the range constraints and defaults. The description adds only the 'chain=base' example and nothing about how limit interacts with the newest-first ordering or how blocks affects scan cost/latency, so the baseline 3 applies.

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 names a specific resource (new liquidity pools), the exact venues (Uniswap v3, Uniswap v2, Aerodrome on Base), the data source (factory PoolCreated/PairCreated events) and the supported chains. It also enumerates the returned fields (pool address, tokens with symbol/decimals, fee tier or stable flag, block, transaction, age, newest first), so an agent knows precisely what this returns without opening the 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?

It gives concrete use cases (spotting new listings, watching pool launches, feeding a new-pair screener) and a safety follow-up ('check token_report before trading'). What it lacks is explicit routing against the sibling pool tools (uniswap_pool, uniswap_liquidity) — there is no statement of when a single-pool lookup is the better choice.

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.