pons-mcp

pons_recent_launches

Scan token launch events newest-first on Robinhood Chain. Filter by deployer or pair token to get token, curve, threshold, block, and transaction details.

Instructions

Scan factory TokenLaunched events newest-first. Optional deployer filter (server-side topic) and pairToken filter (client-side). Returns token, curve, deployer, pairToken, threshold, block, tx hash.

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

Input Schema

Name	Required	Description
`limit`	No	Max results, newest first (default 20, max 100)
`deployer`	No	Filter by deployer address
`pairToken`	No	Filter by pair token address (client-side)
`lookbackBlocks`	No	Blocks to look back from latest (default 50000 ≈ 1.4h at ~10 blocks/s; max 500000)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Sep 15, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations provided, the description carries the behavioral burden. It adds useful context beyond the schema: the event source, newest-first ordering, server-side vs client-side filtering behavior, and the exact output fields. It could mention pagination or error behavior, but for a simple read-only scan this is reasonably transparent.

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 short sentences with no filler. The action, source, ordering, filters, and return fields are covered in a dense, front-loaded structure.

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?

For a zero-required-parameter query tool, the description covers the essential aspects: event source, sort order, optional filters, and return values. The schema covers limit and lookbackBlocks semantics. The main gap is the absence of explicit guidance on when to prefer this over sibling launch-list tools.

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 all four parameters. The description restates the deployer and pairToken filters in prose and adds 'server-side topic' for deployer, but it does not materially enrich parameter meaning beyond what the schema provides.

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 uses a specific verb ('Scan') with a precise resource ('factory TokenLaunched events'), adds ordering ('newest-first'), and lists the returned fields. This clearly distinguishes it from related siblings like pons_recent_graduations, pons_creator_launches, and pons_v1_launches.

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 context is clear: use this tool to scan recent factory TokenLaunched events, with optional deployer and pairToken filters. It does not explicitly contrast itself with the sibling launch-list tools, so an agent must infer when this is the right choice over pons_creator_launches or pons_v1_launches.

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