Skip to main content
Glama

Discover Verified Safe New & Trending DEX Token Pairs

get_new_pairs_alpha
Read-onlyIdempotent

Scans new and boosted liquidity pools on Base, Solana, Ethereum, BSC, Arbitrum, or Polygon, filters scams via GoPlus, and returns verified safe pairs ranked by AlphaScore.

Instructions

Scans newly active and boosted liquidity pools on Base, Solana, Ethereum, BSC, Arbitrum, or Polygon via DexScreener, automatically filters out honeypots and high-tax scams via GoPlus security audits, and returns the top verified safe pairs ranked by AlphaScore. Free to start with zero wallet or setup required (3 free queries/day); unlimited calls supported via optional Base prepaid session.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of verified safe token pairs to return (between 1 and 10, defaults to 5).
networkNoBlockchain network to scan for safe new token pools ("base", "solana", "ethereum", "bsc", "arbitrum", or "polygon"). Defaults to "base".base
paymentProofNoOptional Base USDC transaction hash ("0x...") for high-frequency trading bots needing unlimited calls. Leave empty for automatic free daily queries.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.7.1
    • changedInput schema / properties / paymentProof / description
      Previous value: -"Optional Base USDC transaction hash (\"0x...\") or HTTP 402 payment proof for unlimited calls after your 3 free daily queries."New value: +"Optional Base USDC transaction hash (\"0x...\") for high-frequency trading bots needing unlimited calls. Leave empty for automatic free daily queries."
  2. Addedv1.6.0

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, so the bar is lower, yet the description adds real operational context beyond them: upstream data provenance (DexScreener + GoPlus honeypot/tax filtering), the AlphaScore ranking model, an explicit rate limit of 3 free queries/day, and a payment mechanism requiring no wallet setup. Those are exactly the traits an agent needs to plan calls and handle quota exhaustion.

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?

A single front-loaded sentence that leads with the scan action before piling on sources, filtering, ranking, and pricing. Dense but every clause carries information; it is slightly run-on and could be split for scanability.

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?

With no output schema, the description still communicates what comes back (top verified-safe pairs ranked by AlphaScore) and how many, plus the quota model that governs repeat calls. It stops short of describing the pair record's fields or pagination, a minor gap for a discovery tool with fully documented inputs.

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 description coverage is 100%, so the schema already documents limit (1-10, default 5), network (six-value enum, default base), and paymentProof. The description only corroborates paymentProof in prose ('optional Base prepaid session') without adding format or edge-case detail beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource chain: scans new/boosted liquidity pools across six named chains via DexScreener, screens them through GoPlus, and returns top verified-safe pairs ranked by AlphaScore. This is clearly distinct from siblings like get_token_alpha (single-token alpha) and check_token_security (security audit) — an agent can route correctly without opening any schema.

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?

The free-tier framing (3 free queries/day, unlimited via prepaid Base session) tells the agent about cost/access conditions, and 'newly active and boosted' implies the discovery use case. But it never explicitly says when to choose this over check_token_security or get_token_alpha, nor does it state exclusions — the routing is left to inference from the sibling names.

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