Skip to main content
Glama

Recent launchpad launches

get_recent_launches
Read-only

Fetch recently launched tokens from Robinhood Chain launchpads NOXA and The Odyssey, ordered by block, with filters for count, launchpad, and lookback.

Instructions

Recently launched tokens on Robinhood Chain launchpads (NOXA and The Odyssey), newest first, scanned from on-chain logs.

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_recent_launches"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax launches to return (default 25).
launchpadNoRestrict to one launchpad.
lookbackBlocksNoBlocks to scan back (~30k ≈ 1h; default 30000).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv0.1.1

TDQS

A3.5/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 safety is covered. The description adds genuine context by revealing that results are derived from an on-chain log scan and returned in newest-first order, but it omits lag/coverage caveats and what happens when no launches are found in the lookback window.

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?

A single tightly packed sentence: resource first, launchpad names and ordering immediately after. No filler, no restatement of the title, and the most decision-relevant facts are front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations about returns, the description should say more about what a 'launch' record contains or how results are shaped. It covers source and ordering adequately but leaves the return payload entirely unspecified for a zero-required-parameter listing tool.

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 limit, launchpad, and lookbackBlocks are already fully documented, including defaults and the ~30k≈1h hint. The description only restates the launchpad names and ordering, adding no meaning beyond the schema, so the baseline 3 applies.

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 (recently launched tokens), names the two launchpads (NOXA, The Odyssey), the ordering (newest first), and the data source (on-chain logs). It clearly distinguishes itself from a streaming-style sibling like watch_launches without naming it.

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 implied by 'recently launched' and 'newest first' — an agent can infer this is for discovery of new tokens—but there is no explicit when-to-use/when-not guidance, nor any pointer to an alternative such as watch_launches for ongoing monitoring versus this one-shot scan.

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