Skip to main content
Glama

Arc pools

arc_pools

Arc Sniper Watch: new Uniswap v4 pools on Arc in the last 24 h, who bought each first and how many seconds after it opened, whether the first buyer sold straight back, USDC depth, flags with reasons, and a leaderboard of the fastest first buyers. Read from PoolManager events every five minutes. 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": "arc_pools"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the data source (PoolManager events), a five-minute refresh cadence (useful staleness context), and that access is free. It does not state that the call is read-only, whether it rate-limits or paginates, or how large the returned leaderboard/flag set can get; with zero parameters there is also no way to narrow the payload, which is worth flagging.

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?

It is a single dense sentence, front-loaded with the product name and the core scope ('new Uniswap v4 pools on Arc in the last 24 h'), and every subsequent clause names a distinct returned field rather than padding. It is close to a feature list and the run-on structure makes it slightly harder to scan than a bulleted form would be.

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?

No output schema exists, so the description must enumerate return content, and it does so well: first buyer identity, seconds-to-buy, sell-back flag, USDC depth, reasoned flags, and a fastest-buyer leaderboard. Freshness and cost are covered too; only the response envelope (field names, ordering, size limits) is left unstated, which is a minor gap for a zero-parameter read tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so there is no schema semantics for the description to supplement and the baseline of 4 applies. The description instead spends its words on what comes back, which is the right use of space here.

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 names a concrete resource and a concrete verb: it surveys new Uniswap v4 pools on Arc from the last 24 hours and reports first-buyer timing, sell-back behavior, USDC depth, and flags. That is far more specific than most sibling names such as arc_fresh_launches or arc_trending, though it never explicitly contrasts itself with those neighbors, so an agent must infer that this one is first-buyer/latency focused rather than a general new-pool list.

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?

There is no explicit when-to-use or when-not-to-use statement and no named alternative, so the guidance is only implied by the content (an agent wanting sniper/latency analysis on fresh v4 pools would pick this). The 24-hour window is the only scoping constraint given, and nothing tells the agent which sibling to use instead if it wants raw trades or older pools.

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