Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

space_headlines

Fetch Space.com section headlines for a chosen category slug and return each story's title, URL, summary, author, publication time, and image. Use valid slugs to avoid 400 errors.

Instructions

Get Space.com section headlines. Returns the latest Space.com stories for one category. section is required and takes a slug from space-sections, which joins nested category paths with hyphens, such as astronomy, astronomy-solar-system-mars or stargazing-meteor-showers. Each item has its title, URL, summary, author, publication time and image. Other values return a 400.

Input Schema

NameRequiredDescriptionDefault
sectionYesSpace.com category slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the behavioral burden and does disclose useful traits: it returns the latest stories for one category, enumerates the per-item fields, and warns that invalid values return a 400. It omits auth requirements, rate limits, and pagination, but for a read-only feed the disclosure is solid.

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?

Four tight sentences: purpose first, parameter contract second, worked examples third, return shape and failure mode last. No filler and every sentence carries information.

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

Completeness5/5

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

For a single-parameter tool with no output schema, the description covers purpose, the required input and its derivation, the returned item fields, and the error condition. Nothing an agent needs to invoke it correctly is missing.

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 coverage is already 100% and the enum lists every valid slug, so the baseline is 3. The description goes beyond it by explaining the slug construction rule (nested category paths joined with hyphens) and giving worked examples, which helps an agent map a user's category request to a valid value.

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 states a specific verb and resource ('Get Space.com section headlines') and scopes it to 'one category', which separates it from site-wide siblings like space_news. It does not explicitly name the sibling it is not, but the scope statement is precise enough for an agent to select it correctly.

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 tells the agent that `section` is required and must be a slug obtained from the `space-sections` sibling, which is genuine routing guidance toward the right companion tool. It stops short of stating when to prefer this over space_news or space_article, but the category-scoped context is clear.

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