Skip to main content
Glama

FlowGate

Newest Uniswap v4 pools on Base

recent_launches
Read-onlyIdempotent

Free. Lists the newest ETH/WETH-quoted Uniswap v4 pools on Base from FlowGate's launch index: token, pool id, age in minutes, hook class and swaps so far.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many pools to return (1-20).

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 declare readOnly, idempotent, openWorld and non-destructive, so the description isn't burdened with safety. It adds useful context beyond that: it is a free call, draws from FlowGate's launch index, and enumerates what each record contains (token, pool id, age, hook class, swaps), which fills the gap left by the absent output schema.

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?

One front-loaded sentence with the cost note leading and the resource scope before the field list; there is essentially no filler. Slightly dense field enumeration but nothing wasteful.

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?

For a simple single-parameter read tool with rich annotations and no output schema, listing the returned fields makes it largely self-sufficient. Missing only freshness semantics and any sibling routing guidance.

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?

The single limit parameter is fully documented in the schema (1-20, default 10), so schema coverage does the work. The description adds no meaning beyond it, which makes the baseline 3 appropriate.

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 ("Lists") and a tightly scoped resource ("newest ETH/WETH-quoted Uniswap v4 pools on Base") plus the data source and returned fields. It does not explicitly distinguish itself from sibling launch_preview, but the scope is specific enough that an agent can understand what it does.

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?

Usage is only implied by "newest" — an agent infers this is for browsing freshly created pools. There is no explicit when/when-not guidance and no mention of when to prefer it over launch_preview or how_to_buy_verdict.

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