Femtos

Token launches

list_launches

Read-onlyIdempotent

Latest token launches: Elysium (default) every launchpad, Ascend and every bonding curve inferred from its trades (launchpad name, curve progress, graduation to a DEX pool), or HyperEVM LiquidLaunch (launchpad = liquidlaunch). Each: token, the pool it trades in now (pair), creator, priceUsd, mcapUsd, 24 h volume, holders, top-10 / dev share, dev sold, Ascend progress and on-chain graduation (Ascend rows: ascendGraduation phase, progress, hold, graduatedAt, deadline). sort: newest (default), volume24h, mcap, progress; status: curve, graduated, pool. Next page (newest, Elysium): pass next_cursor as cursor.

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

Input Schema

Name	Required	Description
`q`	No	Elysium: symbol or name contains (case ignored)
`sort`	No	Elysium: newest (default; the cursor pages it), volume24h or mcap of the pool it trades in now, progress toward graduation (a curve; an Ascend launch with status=pool: ascendGraduation.progress, read for the 300 nearest to graduation, the others last); a sort but newest takes launchpad and status only
`layer`	No	hyperevm: LiquidLaunch, or the launches of the launchpad named
`limit`	No	Rows (default 20)
`quote`	No	Elysium: quote token of the pool (USDC, an RWA token…)
`since`	No	Elysium: launched at or after (ms)
`until`	No	Elysium: launched before (ms)
`cursor`	No	Next page: `next_cursor` of the previous answer
`status`	No	Elysium: on its curve, graduated to a DEX pool, or launched straight into a pool (Ascend, an inferred pool launch)
`creator`	No	Elysium: launched by this wallet (creator at launch or current creator)
`network`	No	Elysium network: mainnet or testnet, same answers (testnet USD values null). HyperCore and HyperEVM are always mainnet (default mainnet)
`launchpad`	No	Launchpad name or contract: ascend, vyntra, montra, unknown (inferred launches of no known launchpad)…, any (every launchpad: /v1's default lists Ascend's launch events only until 2026-12-23) (Elysium), liquidlaunch, signal, altfun, unknown, any (HyperEVM, with layer=hyperevm)
`minHolders`	No	Ascended criterion: minimum unique holders (system excluded)
`minMcapUsd`	No	Ascended criterion: minimum market cap, USD (decimal string)
`includeSpam`	No	Show spam tokens (tokens.spam: homoglyph, impostor, phishing name, fake transfers…) flagged spam / spamReason; left out of the list by default
`minVolumeUsd`	No	Ascended criterion: minimum volume since launch, USD
`updatedSince`	No	Elysium: the launches that changed at or after this time (ms, at most an hour back): graduated, traded for the first time, or traded on their curve (reserves and progress); newest first, sort newest only
`maxTop10Share`	No	Ascended criterion: maximum top-10 share of the supply

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 9, 2026

changedInput schema / properties / launchpad / description

Previous value: -"Launchpad name or contract: ascend, vyntra, montra, unknown (inferred launches of no known launchpad)…, any (every launchpad: /v1's default lists Ascend's launch events only until 2026-12-23) (Elysium), liquidlaunch (HyperEVM)"New value: +"Launchpad name or contract: ascend, vyntra, montra, unknown (inferred launches of no known launchpad)…, any (every launchpad: /v1's default lists Ascend's launch events only until 2026-12-23) (Elysium), liquidlaunch, signal, altfun, unknown, any (HyperEVM, with layer=hyperevm)"

changedInput schema / properties / layer / description

Previous value: -"hyperevm = LiquidLaunch"New value: +"hyperevm: LiquidLaunch, or the launches of the launchpad named"

Changed1 schema field changedNov 9, 2026

changedInput schema / properties / sort / description

Previous value: -"Elysium: newest (default; the cursor pages it), volume24h or mcap of the pool it trades in now, progress toward graduation (a curve); a sort but newest takes launchpad and status only"New value: +"Elysium: newest (default; the cursor pages it), volume24h or mcap of the pool it trades in now, progress toward graduation (a curve; an Ascend launch with status=pool: ascendGraduation.progress, read for the 300 nearest to graduation, the others last); a sort but newest takes launchpad and status only"

Changed1 schema field changedNov 9, 2026

addedInput schema / properties / updatedSince

Added value: +{
+  "description": "Elysium: the launches that changed at or after this time (ms, at most an hour back): graduated, traded for the first time, or traded on their curve (reserves and progress); newest first, sort newest only",
+  "maximum": 999999999999999,
+  "minimum": 0,
+  "type": "integer"
+}

Changed3 schema fields changedNov 8, 2026

changedInput schema / properties / launchpad / description

Previous value: -"Launchpad name: ascend (Elysium), liquidlaunch (HyperEVM)"New value: +"Launchpad name or contract: ascend, vyntra, montra, unknown (inferred launches of no known launchpad)…, any (every launchpad: /v1's default lists Ascend's launch events only until 2026-12-23) (Elysium), liquidlaunch (HyperEVM)"

addedInput schema / properties / sort

Added value: +{
+  "description": "Elysium: newest (default; the cursor pages it), volume24h or mcap of the pool it trades in now, progress toward graduation (a curve); a sort but newest takes launchpad and status only",
+  "enum": [
+    "newest",
+    "volume24h",
+    "mcap",
+    "progress"
+  ],
+  "type": "string"
+}

addedInput schema / properties / status

Added value: +{
+  "description": "Elysium: on its curve, graduated to a DEX pool, or launched straight into a pool (Ascend, an inferred pool launch)",
+  "enum": [
+    "curve",
+    "graduated",
+    "pool"
+  ],
+  "type": "string"
+}

Changed1 schema field changedOct 30, 2026

addedInput schema / properties / network

Added value: +{
+  "description": "Elysium network: mainnet or testnet, same answers (testnet USD values null). HyperCore and HyperEVM are always mainnet (default mainnet)",
+  "enum": [
+    "mainnet",
+    "testnet"
+  ],
+  "type": "string"
+}

Changed1 schema field changedOct 22, 2026

removedInput schema / properties / before

Removed value: -{
-  "description": "Deprecated (sunset 31 Jan 2027): use `cursor` / `next_cursor`. Elysium: cursor block:logIndex, the X-Next-Cursor header of the previous page",
-  "type": "string"
-}

Changed19 schema fields changedOct 22, 2026

changedInput schema / properties / before / description

Previous value: -"Deprecated, use cursor: Elysium cursor `next` of the previous page"New value: +"Deprecated (sunset 31 Jan 2027): use `cursor` / `next_cursor`. Elysium: cursor block:logIndex, the X-Next-Cursor header of the previous page"

removedInput schema / properties / before / pattern
```
Removed value: -"^\\d{1,12}:\\d{1,9}$"
```

changedInput schema / properties / creator / description

Previous value: -"Elysium: launched by this wallet"New value: +"Elysium: launched by this wallet (creator at launch or current creator)"

changedInput schema / properties / creator / pattern

Previous value: -"^(0x[0-9a-fA-F]{40}|[a-z0-9][a-z0-9_.-]{0,63}\\.[0-9a-f]{8,64})$"New value: +"^(0x[0-9a-fA-F]{40}|[A-Za-z0-9][A-Za-z0-9_.-]{0,63}\\.[0-9a-fA-F]{8,64})$"

addedInput schema / properties / includeSpam

Added value: +{
+  "description": "Show spam tokens (tokens.spam: homoglyph, impostor, phishing name, fake transfers…) flagged spam / spamReason; left out of the list by default",
+  "type": "boolean"
+}

changedInput schema / properties / launchpad / description

Previous value: -"ascend (Elysium, default) or liquidlaunch (HyperEVM)"New value: +"Launchpad name: ascend (Elysium), liquidlaunch (HyperEVM)"

removedInput schema / properties / launchpad / enum

Removed value: -[
-  "ascend",
-  "liquidlaunch"
-]

addedInput schema / properties / layer

Added value: +{
+  "description": "hyperevm = LiquidLaunch",
+  "enum": [
+    "elysium",
+    "hyperevm"
+  ],
+  "type": "string"
+}

changedInput schema / properties / limit / description

Previous value: -"Rows (default 20, max 100)"New value: +"Rows (default 20)"

changedInput schema / properties / limit / maximum
```
Previous value: -100New value: +200
```

addedInput schema / properties / maxTop10Share

Added value: +{
+  "description": "Ascended criterion: maximum top-10 share of the supply",
+  "exclusiveMinimum": 0,
+  "maximum": 1,
+  "type": "number"
+}

addedInput schema / properties / minHolders

Added value: +{
+  "description": "Ascended criterion: minimum unique holders (system excluded)",
+  "maximum": 999999999,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / minMcapUsd

Added value: +{
+  "description": "Ascended criterion: minimum market cap, USD (decimal string)",
+  "type": "string"
+}

addedInput schema / properties / minVolumeUsd

Added value: +{
+  "description": "Ascended criterion: minimum volume since launch, USD",
+  "type": "string"
+}

changedInput schema / properties / q / description

Previous value: -"Elysium: symbol or name contains"New value: +"Elysium: symbol or name contains (case ignored)"

addedInput schema / properties / quote

Added value: +{
+  "description": "Elysium: quote token of the pool (USDC, an RWA token…)",
+  "pattern": "^0x[0-9a-fA-F]{40}$",
+  "type": "string"
+}

changedInput schema / properties / since / description

Previous value: -"Elysium: launched at or after, Unix ms"New value: +"Elysium: launched at or after (ms)"

changedInput schema / properties / since / maximum

Previous value: -1000000000000000New value: +999999999999999

addedInput schema / properties / until

Added value: +{
+  "description": "Elysium: launched before (ms)",
+  "maximum": 999999999999999,
+  "minimum": 0,
+  "type": "integer"
+}

Changed2 schema fields changedOct 21, 2026

changedInput schema / properties / before / description

Previous value: -"Elysium: cursor `next` of the previous page"New value: +"Deprecated, use cursor: Elysium cursor `next` of the previous page"

addedInput schema / properties / cursor

Added value: +{
+  "description": "Next page: `next_cursor` of the previous answer",
+  "pattern": "^[A-Za-z0-9_-]{2,160}$",
+  "type": "string"
+}

First observedOct 21, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already establish read-only, closed-world, idempotent semantics, so the bar is lower, yet the description still adds real behavior: spam tokens are excluded by default and only surfaced via includeSpam, testnet USD values come back null, and updatedSince is capped at one hour back. The cursor round-trip ('pass next_cursor as cursor') is also disclosed. Missing is anything about result caps or behavior when filters conflict beyond the brief note that newest sort accepts only launchpad and status.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with the resource and sources, which is good, and no sentence is purely decorative. However, it is a single dense run-on packing return fields, sort semantics, status values, and pagination together, with nested parentheticals that make it harder to scan than a short bulleted breakdown would be.

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 18 optional parameters and no output schema, the description does necessary work by enumerating the returned fields (pair, creator, priceUsd, mcapUsd, holders, top-10/dev share, ascendGraduation sub-fields). It leaves the 'Ascended criterion' filters (minHolders, minMcapUsd, minVolumeUsd, maxTop10Share) and q/quote/creator entirely to the schema, which is acceptable at full coverage but means the description alone would not let an agent reason about those filters.

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 coverage is 100% and the schema already carries the rich per-parameter text, including the Elysium scoping, defaults, and enum meanings. The description largely restates sort/status values that the schema defines more precisely and lists row fields rather than clarifying filter interactions. With the schema doing the heavy lifting, 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?

The description opens with a concrete resource ('Latest token launches') and enumerates the two data sources it spans (Elysium bonding-curve/Ascend launches vs. HyperEVM LiquidLaunch), plus the exact per-row fields returned. An agent can tell this is a paginated launch feed rather than a token-detail tool. What it lacks is any explicit differentiation from siblings such as list_new_tokens or list_new_pools, so the boundary is inferred rather than stated.

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 through the sort/status enumerations ('sort: newest (default), volume24h, mcap, progress; status: curve, graduated, pool') and the layer default, which tells an agent how to shape a query. There is no explicit statement of when to choose this tool over a sibling, nor any when-not-to-use or prerequisite guidance. The agent must infer the use case from the field list.

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

All Femtos tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?