Skip to main content
Glama

Latest spaceflight news articles from the Spaceflight News

science_spaceflight_news
Read-only

Latest spaceflight news articles from the Spaceflight News API v4: title, news site, publish date, URL, summary and the total article count. Aggregated from news sites; summaries are the site's own text cut by the API. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax articles, 1 to 20 (default 5)
searchNoOptional keyword, 2 to 60 characters

Output Schema

NameRequiredDescriptionDefault
countNo
sourceNo
articlesNo
checkedAtNo
totalArticlesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/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 reach are covered. The description adds meaningful beyond-annotation context: the $0.002 per-successful-call price, x402/USDC payment mechanics across Base, Solana and 10+ networks, and the fact that failed calls are not charged. It also discloses that summaries are the source site's own truncated text, which is a real behavioral caveat. It stops short of describing latency or rate limits, keeping it below a 5.

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?

The definition is front-loaded with the purpose and returned fields, then adds provenance and pricing. It is dense but every clause carries information; the payment detail is somewhat long but materially relevant to an agent deciding whether to call.

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?

With an output schema present, the description need not re-explain return structure, and it correctly avoids doing so. It covers provenance, truncation of summaries, and cost/payment behavior, which are the non-schema facts an agent needs. Only explicit usage routing is missing.

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 description coverage is 100%, so the schema already fully documents 'limit' (1–20, default 5) and 'search' (2–60 characters). The description mentions no parameter behavior, leaving the baseline of 3 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 gives a specific verb-and-resource ('Latest spaceflight news articles from the Spaceflight News API v4') and enumerates the returned fields (title, site, publish date, URL, summary, total count), so an agent knows exactly what the tool produces. No sibling in the list covers spaceflight news, so no differentiation is needed.

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?

Usage is only implied: 'Latest' suggests a recency-oriented retrieval, and the absence of an alternative is not addressed. There is no explicit statement of when to use this versus another news source or when not to call it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources