Skip to main content
Glama
Sign In
Space Launch & Starlink Tracker

Space Launch & Starlink Tracker

by MAASAI-Labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Starship status

starship_status
Read-only

Check upcoming SpaceX Starship flights with countdowns, recent outcomes, and news headlines.

Instructions

SpaceX Starship: next scheduled flights with countdowns, most recent flight outcomes, and latest news headlines.

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

Input Schema

NameRequiredDescriptionDefault
tzNoIANA timezone for display, e.g. Africa/Lagos, America/New_York. UTC always shown too.
newsLimitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-data sourcing are covered. The description adds no behavioral context beyond that: no mention of caching, freshness, rate limits, or the shape of the countdown/outcome data. With annotations doing the safety work, this leaves little added value.

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?

A single front-loaded sentence listing exactly what is returned, with no filler. Every clause earns its place.

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

Completeness2/5

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

For a read-only aggregator with two parameters, no output schema, and sibling launch tools, the description is too thin. It never resolves the overlap with upcoming_launches/next_launch and never covers the newsLimit parameter, leaving the agent to guess scope and limits.

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 coverage is 50%: tz is fully described in the schema, but newsLimit has only type/bounds. The description does not mention either parameter, so it fails to compensate for the undocumented newsLimit parameter. Baseline 3 applies given partial schema coverage.

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 the resource (SpaceX Starship) and states three concrete outputs: upcoming flights with countdowns, recent outcomes, and news headlines. It is specific about scope but does not differentiate itself from siblings like upcoming_launches or next_launch, which likely overlap in launch-listing behavior.

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?

Implicit usage is clear from the content (Starship-specific status), but the description never says when to pick this over upcoming_launches or next_launch, or whether it is Starship-only vs. all launches. No exclusions or alternatives are named.

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

Deploy Server

Other Tools