Skip to main content
Glama
Sign In

Spaceflight News

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Search Articles

search_articles
Read-onlyIdempotent

Full-text search spaceflight news articles aggregated from dozens of sources (Spaceflight Now, NASASpaceflight, NASA, SpaceX, Blue Origin, ESA, and more). Filter by source, publish date, and featured status. Newest first. Keyless.

Input Schema

NameRequiredDescriptionDefault
limitNoMax articles to return (default 10, max 25).
searchNoFull-text query, e.g. "starship", "artemis", "mars sample return". Optional — omit to list recent articles.
news_siteNoFilter to a single source name, e.g. "Spaceflight Now", "NASASpaceflight". Use list_sources to discover names.
featured_onlyNoIf true, return only editorially featured articles.
published_afterNoOnly articles published on/after this ISO date or datetime, e.g. "2026-01-01" or "2026-01-01T00:00:00Z".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "search": "starship"
+  },
+  {
+    "featured_only": true,
+    "limit": 15,
+    "published_after": "2026-01-01",
+    "search": "artemis"
+  }
+]
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint, openWorldHint, idempotentHint, destructiveHint. The description adds value by stating 'Newest first' ordering and 'Keyless' access, complementing the annotations without contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence efficiently conveys the main functionality, sources, and filtering options. Could be slightly more structured (e.g., bullet points) but remains clear and concise.

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

Completeness3/5

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

The description covers search scope, sources, and filters but omits details on return format, pagination, or default behavior beyond 'newest first'. Given no output schema, additional context would improve completeness.

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?

All parameters have descriptions in the input schema (100% coverage). The tool description provides overarching context but adds no new semantic information beyond what the schema already provides. Baseline 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 clearly states it performs full-text search over spaceflight news articles from multiple specific sources, with filtering options. It distinguishes itself from siblings like 'get_article' (single article retrieval) and 'list_sources' (source listing).

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 implies use for searching articles with filtering, but lacks explicit guidance on when to use this tool versus siblings or alternatives. It mentions 'Keyless' indicating no auth needed, but no direct comparisons.

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

All Spaceflight News 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