Skip to main content
Glama

Watch for live launches

watch_launches
Read-only

Monitors NOXA and The Odyssey for new token launches, waits up to a set time or launch limit, and returns those seen; falls back to a recent launch if none appear.

Instructions

Watch NOXA + The Odyssey live for new token launches, blocking up to waitSeconds (or until limit launches are seen), then returns what appeared. Falls back to the most recent launch if none fire in the window.

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

Input Schema

NameRequiredDescriptionDefault
limitNoStop early after this many (default 20).
launchpadNoRestrict to one launchpad.
waitSecondsNoHow long to watch (default 20, max 120).
includeRecentIfEmptyNoIf nothing launches in the window, return the latest recent launch (default true).

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

A4.2/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds important behavior: the call blocks up to waitSeconds, stops early at limit, and falls back to the most recent launch if nothing fires. It does not discuss rate limits or authentication, but the core behavioral traits are disclosed.

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 the core action and followed by the blocking/fallback behavior. There is no redundant or filler wording.

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 read-only, open-world watcher with no output schema, the description covers the essential behavior: what it watches, how long it blocks, when it stops, and what happens if nothing appears. Return shape is only broadly described, but the key operational details are present.

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 reinforces waitSeconds, limit, and the fallback behavior, but it does not add syntax or meaning beyond what the schema provides, so the baseline of 3 is appropriate.

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 ("Watch") and resource ("live token launches") and names the launchpads NOXA and The Odyssey. It also distinguishes the live, blocking behavior from a simple recent-launch lookup by describing the wait window and fallback.

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 clearly establishes the live-watching use case and explains the blocking wait plus fallback behavior. It does not explicitly name an alternative such as get_recent_launches or state when not to use this tool, so it stops short of full when/when-not guidance.

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