Skip to main content
Glama

x402-services

by ai.firmbrain

snipe_newpairs

Snipe new token launches: the freshest liquidity pools on a chain, newest first, with pool age in seconds, price, FDV, and liquidity. Send { chain, limit?, minLiquidityUsd? }. Supports Base, Solana, Ethereum, Arbitrum, BSC, Polygon, Optimism, Avalanche, and Robinhood Chain. The core new-pair detection signal for sniping bots and trading agents. [x402 paid tool — price $0.005; POST /api/snipe/newpairs]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainNoChain: base (default), solana, ethereum, arbitrum, bsc, polygon, optimism, avax, robinhood
limitNoMax pools, default 15 (max 50)
minLiquidityUsdNoOnly pools with at least this much liquidity (USD)

TDQS

A4.4/5.0
Behavior4/5

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

No annotations exist, so the description carries full burden. It discloses that it is a paid tool with price $0.005 and POST method. It describes output fields (pool age, price, FDV, liquidity) and implies read-only behavior. No contradictions.

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 sentences plus a short pricing note. Every sentence adds information: purpose+output, parameters, supported chains, use case, and pricing. No wasted words.

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?

Given no output schema, the description mentions key output fields. It covers parameters, supported chains, and use case. Lacks pagination details but limit parameter suffices. For a simple list tool, it is fairly complete.

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?

Schema description coverage is 100%. The description adds value beyond schema by stating default values (chain defaults to 'base', limit defaults to 15 max 50), listing specific supported chains, and explaining the minLiquidityUsd filter.

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 clearly states the tool lists new token launches/liquidity pools, sorted newest first, with key metrics (age, price, FDV, liquidity). It distinguishes from siblings by calling itself 'the core new-pair detection signal' and specifying supported chains.

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?

The description provides clear context for when to use the tool: 'for sniping bots and trading agents' as the core new-pair signal. However, it does not explicitly state when not to use it or compare to siblings like snipe_search or snipe_pair.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All x402-services toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.5/5.0
Disambiguation4/5

Tools are organized by domain prefix (e.g., 'crypto_', 'rh_', 'snipe_'), which helps distinguish between areas. Within each domain, they serve distinct purposes, though some overlap between domains exists (e.g., price data appears in multiple groups). Overall, an agent can navigate effectively.

Naming Consistency5/5

All tool names follow a consistent snake_case pattern with a domain prefix and a verb_noun combination (e.g., 'compliance_risk', 'rh_stock', 'snipe_honeypot'). This makes the API predictable and easy to explore.

Tool Count2/5

With 159 tools, the server is extremely large. While the broad scope of web3 and utility functions justifies many tools, the count is significantly above the typical range for a coherent toolkit, potentially overwhelming agents and increasing selection error.

Completeness4/5

The toolkit covers a wide range of web3 operations: crypto, DeFi, compliance, safety, scheduling, memory, etc. There are no obvious major gaps for its intended purpose, though some niche areas might be missing.

Resources