Skip to main content
Glama

sol_new_pairs

Read-onlyIdempotent

Freshly-created Solana pools (incl. pump.fun) — snipe, then verify — The newest Solana DEX pools (via GeckoTerminal), each with its mint, age, liquidity, 24h volume and a pump.fun flag — the fresh-launch feed sniper bots watch. Optional: limit (1–30) and minLiquidityUsd to filter dust. New ≠ safe: pair it with sol-token-verdict before buying. No feed → not charged. Not advice. Priced $0.02 per call over x402 on Base; send a prepaid x-credit-token header for unlimited calls, or get 1 free call/day per tool. No API key required.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax pools (1–30)
minLiquidityUsdNoMin liquidity USD

Output Schema

NameRequiredDescriptionDefault
dataNoThe result payload. Shape is service-specific; every field is documented in the tool description.
serviceNoThe service id that answered.
checkedAtNoISO-8601 timestamp of when the underlying reads were taken.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Goes well beyond the readOnly/openWorld annotations by disclosing the upstream data source (GeckoTerminal), the exact payload fields, a no-feed-no-charge policy, x402 pricing on Base, the prepaid x-credit-token header for unlimited calls, a free call/day, and that no API key is needed. That is exactly the operational context an agent needs before invoking a paid external feed.

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?

Front-loaded with purpose, then caveats, then payment terms, with zero filler sentences. There is mild redundancy in restating 'freshly-created Solana pools' and 'newest Solana DEX pools' in the opening lines, but overall it remains dense and scannable.

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?

An output schema exists, so return fields need not be re-explained, and the description nonetheless summarizes them. Payment, auth, free-tier, and safety caveats are all covered; only deeper operational details (latency, rate limits, freshness window) are absent, which is acceptable for this scope.

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 coverage is 100%, so the baseline is 3, and the description adds purpose: limit caps results at 1–30 and minLiquidityUsd exists to 'filter dust', which tells the agent why to set it rather than just what it is. Marginal but genuine value on top of the schema.

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 resource (newest Solana DEX pools via GeckoTerminal, including pump.fun) and enumerates the returned fields (mint, age, liquidity, 24h volume, pump.fun flag). It differentiates from its natural companion by naming sol-token-verdict for verification, though it does not explicitly contrast with the similar-sounding sibling new_tokens.

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?

Gives a clear workflow: use it as the fresh-launch feed for sniping, then pair with sol-token-verdict before buying. The 'New ≠ safe' warning establishes when not to act on the output alone. No explicit exclusion versus other listing tools, but context is strong.

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