Skip to main content
Glama

space_headlines

Read-only

Current Space headlines for one public section; section must come from space_sections.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "section": "<section>"
    },
    "name": "space_headlines"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectionYesSpace.com category slug. Documented values: astronomy, astronomy-black-holes, astronomy-dark-universe, astronomy-exoplanets, astronomy-galaxies, astronomy-hubble-space-telescope, astronomy-james-webb-space-telescope, astronomy-solar-system, astronomy-solar-system-asteroids, astronomy-solar-system-comets, astronomy-solar-system-dwarf-planets, astronomy-solar-system-earth, astronomy-solar-system-jupiter, astronomy-solar-system-mars, astronomy-solar-system-mercury, astronomy-solar-system-moon, astronomy-solar-system-neptune, astronomy-solar-system-pluto, astronomy-solar-system-saturn, astronomy-solar-system-sun, astronomy-solar-system-uranus, astronomy-solar-system-venus, astronomy-stars, entertainment, entertainment-space-books, entertainment-space-games, entertainment-space-movies-shows, entertainment-space-toys-lego, science, science-astrophysics, science-climate-change, science-particle-physics, science-weather, space-exploration, space-exploration-human-spaceflight, space-exploration-launches-spacecraft, space-exploration-missions, space-exploration-missions-apollo, space-exploration-missions-artemis, space-exploration-missions-asteroid-comet-missions, space-exploration-missions-international-space-station, space-exploration-missions-mars-rovers, space-exploration-missions-new-horizons, space-exploration-missions-parker-solar-probe, space-exploration-missions-space-shuttle, space-exploration-missions-voyager, space-exploration-private-spaceflight, space-exploration-satellites, space-exploration-search-for-life, stargazing, stargazing-astrophotography, stargazing-auroras, stargazing-constellations, stargazing-eclipses, stargazing-eclipses-lunar-eclipses, stargazing-eclipses-solar-eclipses, stargazing-meteor-showers, stargazing-skywatching-kit, technology, technology-aerospace, technology-drones.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / section / description
      Added value: +"Space.com category slug. Documented values: astronomy, astronomy-black-holes, astronomy-dark-universe, astronomy-exoplanets, astronomy-galaxies, astronomy-hubble-space-telescope, astronomy-james-webb-space-telescope, astronomy-solar-system, astronomy-solar-system-asteroids, astronomy-solar-system-comets, astronomy-solar-system-dwarf-planets, astronomy-solar-system-earth, astronomy-solar-system-jupiter, astronomy-solar-system-mars, astronomy-solar-system-mercury, astronomy-solar-system-moon, astronomy-solar-system-neptune, astronomy-solar-system-pluto, astronomy-solar-system-saturn, astronomy-solar-system-sun, astronomy-solar-system-uranus, astronomy-solar-system-venus, astronomy-stars, entertainment, entertainment-space-books, entertainment-space-games, entertainment-space-movies-shows, entertainment-space-toys-lego, science, science-astrophysics, science-climate-change, science-particle-physics, science-weather, space-exploration, space-exploration-human-spaceflight, space-exploration-launches-spacecraft, space-exploration-missions, space-exploration-missions-apollo, space-exploration-missions-artemis, space-exploration-missions-asteroid-comet-missions, space-exploration-missions-international-space-station, space-exploration-missions-mars-rovers, space-exploration-missions-new-horizons, space-exploration-missions-parker-solar-probe, space-exploration-missions-space-shuttle, space-exploration-missions-voyager, space-exploration-private-spaceflight, space-exploration-satellites, space-exploration-search-for-life, stargazing, stargazing-astrophotography, stargazing-auroras, stargazing-constellations, stargazing-eclipses, stargazing-eclipses-lunar-eclipses, stargazing-eclipses-solar-eclipses, stargazing-meteor-showers, stargazing-skywatching-kit, technology, technology-aerospace, technology-drones."
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds two useful bits of context ('Current' freshness and single-public-section scoping), but does not describe pagination or result volume.

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 tight sentence with the scope stated first and the input constraint second; every clause earns its place with no filler.

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?

An output schema exists, so return values need no explanation, and annotations cover the safety profile. The description covers the input dependency and the single-section scope; only minor freshness/volume details are absent.

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 100% and the section property already enumerates every valid slug, so the schema carries the parameter documentation. The description only adds the constraint that values must originate from space_sections, which is a marginal but real addition beyond the schema.

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 gives a specific verb (headlines) and resource (current Space headlines) bounded to 'one public section', which is enough to tell it apart from a full-feed sibling. It does not explicitly contrast itself with space_news or space_article, so it stops short of a full 5.

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?

It provides a concrete prerequisite: 'section must come from space_sections', effectively routing the agent to the correct tool to obtain valid input. It stops short of stating when to prefer this over space_news, so no explicit exclusion is given.

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.