Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

space_article

Retrieve Space.com article content by canonical URL as structured JSON with title, authors, dates, images, and body paragraphs.

Instructions

Get Space.com article content. Returns a Space.com article by canonical url in any of the site's URL shapes, including older .html reference pages: title, description, section, authors, publication and update times, image and body paragraphs. /news/live/ pages return only their introductory paragraphs, and membership-gated content returns only its public preview.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Space.com article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations, the description carries full burden and does so well: it discloses that any of the site's URL shapes work including older .html reference pages, that /news/live/ pages yield only introductory paragraphs, and that membership-gated content returns only the public preview. These are non-obvious edge-case behaviors an agent needs before calling.

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?

Front-loaded with the core purpose in the first sentence, followed by return fields and then caveats. Two dense sentences with no filler; every clause 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-required-param read tool with no output schema, the description covers purpose, input flexibility, returned fields, and the significant content-truncation caveats. 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 100% and the single param is documented, so baseline is 3, but the description adds real meaning by clarifying the URL may be in 'any of the site's URL shapes, including older .html reference pages' — more permissive and useful than the schema's bare 'Canonical Space.com article URL'.

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?

States a specific verb (Get) and resource (Space.com article content) and enumerates the returned fields, so an agent immediately knows this is the single-article fetcher rather than a list endpoint like space_headlines or space_news. No ambiguity about what the tool produces.

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 implied by the schema (a URL is required, so this fetches one specific article) but the description never states when to use it versus siblings such as space_headlines/space_news for discovery. There are no explicit when/when-not statements or named alternatives.

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