Skip to main content
Glama

spacex

by io.github.pipeworx-io

Get Latest Launch

get_latest_launch
Read-onlyIdempotent

Get the most recent SpaceX launch. Returns launch name, date (UTC), success status, mission details, rocket, launch pad, and media links (webcast, article, wikipedia).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesLaunch name
linksYes
rocketYesRocket ID
detailsYesLaunch details
successYesLaunch success status
date_utcYesLaunch date in UTC

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "date_utc": {
+      "description": "Launch date in UTC",
+      "type": "string"
+    },
+    "details": {
+      "description": "Launch details",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "links": {
+      "properties": {
+        "article": {
+          "description": "Article link",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "webcast": {
+          "description": "Webcast link",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "wikipedia": {
+          "description": "Wikipedia link",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "webcast",
+        "article",
+        "wikipedia"
+      ],
+      "type": "object"
+    },
+    "name": {
+      "description": "Launch name",
+      "type": "string"
+    },
+    "rocket": {
+      "description": "Rocket ID",
+      "type": "string"
+    },
+    "success": {
+      "description": "Launch success status",
+      "type": [
+        "boolean",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "name",
+    "date_utc",
+    "success",
+    "details",
+    "rocket",
+    "links"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {}
+]
  3. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so safety is clear. The description adds return field details but no additional behavioral traits such as potential null results or dynamic nature of 'latest'.

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 action, followed by a concise list of return fields. No unnecessary words.

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?

For a zero-parameter, read-only tool with an output schema and annotations, the description provides sufficient detail about what is returned. It is complete within the context of structured data.

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?

The tool has zero parameters, so the baseline is 4. The description doesn't need to explain any parameters and none are present.

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 'Get' with a clear resource 'most recent SpaceX launch', distinguishing it from sibling tools like get_next_launch and get_past_launches. It clearly states what the tool returns without ambiguity.

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?

The description implies usage for retrieving the latest launch but does not explicitly contrast with get_next_launch or get_past_launches. It provides clear context for the 'most recent' specific launch, yet lacks exclusionary or alternative guidance.

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

All spacex 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.6/5.0
Disambiguation2/5

The server is named 'spacex' but contains a vast number of tools unrelated to SpaceX, such as polymarket arbitrage, npm package scanning, and claim validation. Users and agents would struggle to determine whether this server is for SpaceX data or general-purpose queries.

Naming Consistency2/5

The SpaceX-specific tools follow a consistent 'get_' pattern, but the majority of tools use varied naming conventions (e.g., 'ask_pipeworx', 'bet_research', 'remember', 'subscribe'). No unifying pattern across the set.

Tool Count3/5

36 tools is a moderately large count, not extreme. However, many tools are unrelated to the server's namesake, making the set feel bloated and unfocused. The count could be trimmed to improve coherence.

Completeness2/5

For the SpaceX domain, the coverage is decent (launches, rockets, crew, Starlink). But the server's purpose is unclear—there are glaring gaps in a unified vision, as the Pipeworx tools are not integrated into a coherent SpaceX theme.

Resources