Skip to main content
Glama

launches

by io.github.pipeworx-io

Get Past Launches

get_past_launches
Read-onlyIdempotent

Fetch rocket launches that have already flown, sorted newest-first, from Launch Library 2. launches holds only those with a confirmed outcome — successful, failed or partial failure — so counting them answers "how many launches happened". A launch whose scheduled time has passed but whose outcome upstream has not yet confirmed is reported separately in unconfirmed with its current status, rather than being counted as flown. Use since and until to bound a window (ISO dates). Returns launch name, time, status, pad, rocket type, and mission description. Default 10 results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of launches to return (default 10)
sinceNoOptional. Only launches at or after this time (ISO 8601, e.g. "2026-08-01" or "2026-08-01T00:00:00Z"). Use with `until` to count launches in a window.
untilNoOptional. Only launches before this time (ISO 8601). Defaults to now, since this tool covers launches that have already happened.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
totalYesTotal count of past launches available
launchesYesList of past launches

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint, idempotentHint, etc.), the description adds meaningful behavioral details: the data source (Launch Library 2), sorting order, confirmed-outcome filtering, separate `unconfirmed` reporting, and the fact that `until` defaults to now. This significantly aids the agent in understanding tool behavior.

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?

The description is front-loaded with the core purpose and each sentence adds value: clarifies confirmed/unconfirmed semantics, windowing, return fields, and default limit. It is detailed but not verbose.

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

Completeness5/5

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

The description fully covers the tool's nuanced behavior (confirmed versus unconfirmed launches), which is essential for correct use. It also mentions return fields even though an output schema exists, providing a complete picture for the agent.

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?

The input schema already provides 100% parameter coverage with detailed descriptions and examples. The description adds a brief reminder about using `since`/`until` for a window and the default limit, but this largely restates schema information without introducing new semantics.

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 clearly states the tool's function: 'Fetch rocket launches that have already flown, sorted newest-first, from Launch Library 2.' This is a specific verb+resource+scope that distinguishes it from sibling tools like get_upcoming_launches and search_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 description provides clear context on when to use the tool: for counting or listing launches with confirmed outcomes, and explains the distinction between `launches` and `unconfirmed`. It also explains how to use `since`/`until` for windowed queries, though it doesn't explicitly mention alternatives like get_upcoming_launches or search_launches.

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

All launches toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation2/5

Several tools have significantly overlapping purposes: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all perform data retrieval, with beta currently identical to stable. The polymarket_* family and bet_research also blur boundaries, and discover_tools vs suggest_questions both handle discovery. Despite detailed descriptions, agents are likely to misselect among these overlapping options.

Naming Consistency3/5

All tools use snake_case, but conventions are mixed: some start with verbs (get_launch, search_launches, ask_pipeworx), others are noun phrases (entity_profile, pipeworx_trending), and there are versioned suffixes (ask_pipeworx_beta). While each domain group has internal consistency, the overall set lacks a unified pattern.

Tool Count2/5

35 tools is excessive for a server named 'launches'—only 4 tools (get_launch, get_past_launches, get_upcoming_launches, search_launches) actually relate to space launches. The remaining 31 tools cover unrelated domains like prediction markets, company profiles, and memory, making the count inappropriate and diluting the server's focus.

Completeness2/5

For the claimed launch domain, the set provides only basic list/detail/search operations and lacks useful launch features like filtering by agency, date range, or launch site. More critically, the inclusion of 31 unrelated tools creates a fragmented surface with obvious dead ends—an agent expecting a launch-focused server would find most tools irrelevant.

Resources