Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

space_sections

List Space.com sections and subcategories to find valid slugs for space-headlines queries. Returns each category's name, URL, and hyphenated slug path.

Instructions

Get Space.com sections. Lists the Space.com categories that space-headlines accepts, from astronomy, entertainment, science, space-exploration, stargazing and technology down to their subcategories. Each entry has a slug, a display name and the category url. Slugs join the nested path with hyphens, so astronomy-solar-system-mars maps to /astronomy/solar-system/mars.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden, and it does disclose meaningful behavior: the return shape (slug, name, url) and the slug-to-path convention. It never states side-effect freedom or read-only status, but for a listing endpoint the format disclosure is the substantive part.

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?

Three front-loaded sentences with no filler; the purpose leads and the format detail follows. The six-category enumeration is slightly verbose but directly informs coverage, so it mostly earns its place.

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 no-param, no-output-schema listing tool, the description supplies exactly what is missing: the return fields (slug, name, url) and the slug/path mapping. Nothing an agent needs to call and consume it is absent.

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?

Zero parameters, so baseline is 4. The schema is empty and fully covered, and the description adds no parameter semantics because none exist.

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/List) and resource (Space.com sections/categories), and explicitly ties itself to the `space-headlines` sibling it feeds. An agent can distinguish it from space_news/space_article/space_author without opening any schema.

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 implies the use case clearly: this lists the categories that `space-headlines` accepts, so it functions as the discovery step before calling headlines. It gives context but stops short of explicit when-not-to-use or naming an alternative listing tool.

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