Skip to main content
Glama

launches

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Search Launches

search_launches
Read-onlyIdempotent

Search launches by keyword (rocket name, mission, agency). Returns matching launches with name, time, status, pad, rocket, and mission.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of results to return (default 10)
queryYesSearch keyword (e.g. "Falcon 9", "Artemis", "ISS")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query string used
totalYesTotal count of matching launches
launchesYesList of matching launches

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "launches": {
+      "description": "List of matching launches",
+      "items": {
+        "properties": {
+          "id": {
+            "description": "Launch Library 2 launch UUID",
+            "type": "string"
+          },
+          "location": {
+            "description": "Launch location/facility name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "location_country": {
+            "description": "Launch location country code",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "mission_description": {
+            "description": "Mission objectives and details",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "mission_name": {
+            "description": "Mission name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "mission_type": {
+            "description": "Mission type classification",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "name": {
+            "description": "Launch name",
+            "type": "string"
+          },
+          "net": {
+            "description": "Launch date/time (ISO 8601)",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "pad_name": {
+            "description": "Launch pad name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "rocket_name": {
+            "description": "Rocket full name or configuration name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "status": {
+            "description": "Launch status name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "status_description": {
+            "description": "Detailed status description",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "id",
+          "name"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "query": {
+      "description": "Search query string used",
+      "type": "string"
+    },
+    "total": {
+      "description": "Total count of matching launches",
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "query",
+    "launches"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "limit": 10,
+    "query": "Falcon 9"
+  },
+  {
+    "query": "Artemis"
+  }
+]
  3. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already document read-only, idempotent, and non-destructive behavior. The description adds the return field list, which is useful, but does not disclose additional behavioral traits such as whether the search covers past/upcoming launches, pagination, or rate limits. With annotations covering safety, this meets the baseline.

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 concise sentences that front-load the core action and resource, list return fields, and avoid redundant wording. Highly efficient and well-structured.

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?

The description, combined with full schema coverage, output schema, and annotations, provides sufficient information for a simple search tool. However, it leaves ambiguity about whether the search includes past, upcoming, or both types of launches—a relevant detail given the presence of dedicated past/upcoming siblings.

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 descriptions cover both parameters completely (100% coverage) with examples and defaults. The tool description's mention of 'rocket name, mission, agency' partially overlaps with the schema's examples, adding marginal semantic value beyond the schema.

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 action (search), the resource (launches), and the search criteria (keyword: rocket name, mission, agency). It also lists the return fields, distinguishing it from sibling tools like get_launch which appear to retrieve specific launches by ID.

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?

Provides clear context for when to use the tool (when you have a keyword to search launches) and subtly differentiates from specific retrieval siblings, but does not explicitly name alternatives or state when not to use it. The context is clear enough for most use cases.

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
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