Skip to main content
Glama

APEX DeFi, DefiLlama & 8-Chain EVM Intel

Dex new pools

dex_new_pools
Read-onlyIdempotent

Live newly created or trending DEX pools from GeckoTerminal across Base, Solana, Ethereum, Arbitrum, Optimism, Polygon and BSC. $0.005 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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
modeNonew_pools (default) or trending_pools
limitNo1-20
networkNobase, solana, eth, arbitrum, optimism, polygon_pos, bsc (default base)
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare readOnly/openWorld/idempotent/non-destructive, and the description adds genuinely new behavioral facts: a per-call price of $0.005, the x402 payment rail and accepted assets (USDC on Arc/Base/Solana, XNT on X1), and that the purchase completes inside the same call. It does not explain payment expiry, retry semantics, or what happens on a failed settlement. Note a mild tension with readOnlyHint=true, since the tool can move funds, but the underlying data operation remains a read.

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?

Purpose is front-loaded in the first clause and the payment mechanics follow logically. It is dense but nearly every clause carries information; the pricing/protocol sentence is long and could be split, but nothing is truly wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-required-parameter, no-output-schema tool, the calling contract (payment flow, defaults, networks) is well covered. However, with no output schema the description never characterizes the returned pool records (fields such as liquidity, volume, pool address), leaving the agent blind to response shape; payment failure behavior is also unaddressed.

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 all four parameters are already documented, including defaults. The description only adds workflow meaning for `payment` (how to obtain and sign it) and never addresses `mode`, `limit`, or `network`; worse, its chain names ('Ethereum', 'Polygon') differ from the schema enum values ('eth', 'polygon_pos'), which could mislead. 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?

The description opens with a specific verb and resource ('Live newly created or trending DEX pools from GeckoTerminal') and enumerates the supported chains, so an agent knows exactly what it retrieves. It does not name any sibling tool, but the listed siblings (arc_*, agora_*, agent_*) are in unrelated domains, so confusion risk is low.

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 call guidance for the payment handshake: 'Call once without `payment` for the terms, sign them with your own wallet, call again with `payment`.' That is an explicit two-step procedure. What is missing is any when-to-use / when-not guidance (e.g. new_pools vs trending_pools selection) or what to do if the signed payment is rejected.

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.