Skip to main content
Glama

new_launches

Read-only

Newest tokens launched on BNB Chain (PancakeSwap V2) and Base (Uniswap V2), each scanned for honeypots, taxes, liquidity and owner powers a few minutes after its pool is created. Newest first.

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

Input Schema

NameRequiredDescriptionDefault
chainNobsc = BNB Chain, base = Base, all = bothall
limitNohow many launches to return (1-50)
api_keyNoNovaquill API key for paid credits (optional; 10 free calls/day without)
min_scoreNoonly return tokens with a safety score of at least this (0-100, higher is safer)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / api_key / description
      Added value: +"Novaquill API key for paid credits (optional; 10 free calls/day without)"
    • addedInput schema / properties / chain / description
      Added value: +"bsc = BNB Chain, base = Base, all = both"
    • addedInput schema / properties / limit / description
      Added value: +"how many launches to return (1-50)"
    • changedInput schema / properties / min_score / description
      Previous value: -"only return tokens scoring at least this"New value: +"only return tokens with a safety score of at least this (0-100, higher is safer)"
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description does add real context beyond them — the scan happens a few minutes after pool creation, covers honeypots, taxes, liquidity and owner powers, and results come newest-first — but it stays silent on rate limits/free-tier behavior (only visible in the schema) and on whether results update or are a snapshot.

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?

Two tight sentences with zero filler; the resource, venues and scan coverage are front-loaded and the ordering note closes it out. Every clause carries information.

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 usefully implies what each entry contains (safety scan across honeypots, taxes, liquidity, owner powers) and how results are ordered, which is enough for an agent to call it. It could go slightly further on freshness/caching and what happens when min_score filters everything out.

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 chain, limit, min_score and api_key are all documented in the schema, setting the baseline at 3. The description adds no syntax or semantic detail for any parameter; the only extra signal is ordering ('newest first'), which is not itself a parameter.

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+resource ('newest tokens launched') with the exact venues covered (PancakeSwap V2 on BNB Chain, Uniswap V2 on Base) and the scan dimensions applied to each. It never mentions the sibling token_risk, so the agent gets a clear purpose but no explicit differentiation from that tool.

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: 'Newest first' and 'a few minutes after its pool is created' suggest a discovery/scanning feed for fresh tokens, but there is no statement of when to pick this over token_risk, nor any exclusions or prerequisites.

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