Skip to main content
Glama

POPULAR (Sui memecoin launchpad)

Recent launches

recent_launches
Read-onlyIdempotent

Tokens launched on POPULAR (the stable launch feed /api/v1/launches). Without after: the newest limit launches. With after (a next from an earlier answer): the launches after that cursor, oldest first, to follow new ones.

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

Input Schema

NameRequiredDescriptionDefault
afterNoThe `next` cursor of the previous page.
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare this a safe, idempotent, read-only, open-world read, so the safety profile is covered. The description adds behavior the annotations cannot: result ordering flips between newest-first and oldest-first depending on `after`, and the feed is described as 'stable' for incremental following. It omits rate limits and error behavior, keeping it below a 5.

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 sentences, front-loaded with what the tool returns, then the two cursor modes. The parenthetical endpoint reference earns its place by pinning down which feed is meant. No filler or repetition.

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?

There is no output schema, and the description partially compensates by revealing that responses carry a `next` cursor and are ordered. It does not say what fields a launch record contains or how an absent `next` should be read, which is a minor remaining gap for a two-parameter feed reader.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50% – only `after` is documented in the schema, while `limit` carries no description. The description compensates by explaining that `limit` bounds the newest results and that `after` takes a `next` cursor from a prior answer, plus the non-obvious consequence that ordering reverses with the cursor. That is meaningful semantics beyond the schema.

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 names a specific resource and scope: tokens launched on POPULAR, identified as the stable launch feed at /api/v1/launches. An agent can immediately tell this is a launch-feed reader rather than a trade, candle, or token-lookup tool. It stops short of naming any sibling to contrast against, so it lands at 4 rather than 5.

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?

It gives a clear when-to-use split: call without `after` for the newest launches, and call with `after` to follow new ones incrementally. That is genuine operational guidance an agent can act on. It offers no exclusions, such as directing token-specific or filtered lookups to search_tokens/get_token instead.

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