Skip to main content
Glama
Sign In
Cosmik — Live Space Data

Cosmik — Live Space Data

by crashedfox
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Launch news & recaps

get_launch_news
Read-onlyIdempotent

Retrieve rocket-launch news articles, including previews and post-launch recaps. Optionally filter by search term for specific missions, rockets, or providers.

Instructions

Latest rocket-launch news articles (previews and post-launch recaps) from Cosmik, optionally filtered by a search term (mission, rocket, or provider name).

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of articles to return (1-10, default 5)
queryNoSearch term matched against article titles, e.g. 'Starship', 'Crew', 'Ariane'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already cover read-only, open-world, idempotent, non-destructive behavior. The description adds context about the type of content (previews and recaps) but does not introduce new behavioral traits. No contradictions with annotations.

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?

The description is a single 14-word sentence that efficiently conveys the tool's purpose, source, and optional filter. No redundant information; every word earns its place.

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?

Given the tool's simplicity, no required parameters, and comprehensive annotations, the description is largely complete. It informs about the source and content type, but lacks details about the return structure (e.g., fields in each article). However, this is not critical for a basic news retrieval tool.

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?

Schema description coverage is 100% with detailed descriptions for both 'limit' and 'query'. The description reinforces the query parameter by specifying it filters by 'mission, rocket, or provider name', adding value beyond the schema that only mentions matching article titles. This extra context improves parameter understanding.

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 tool retrieves 'Latest rocket-launch news articles (previews and post-launch recaps) from Cosmik' with optional search filter. It is specific about the resource (news articles) and distinguishes from siblings like get_next_launches and get_iss_passes, which provide different launch data.

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 does not explicitly state when to use this tool versus siblings. While the names and content imply that this is for news articles and get_next_launches for schedules, there is no explicit guidance on alternatives or exclusions. Usage is partially implied but not fully articulated.

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