Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

rawstory_sections

Retrieve the 15 Raw Story section and topic hubs, including slugs, names, and URLs, to identify valid categories for headline queries.

Instructions

Get Raw Story sections. Lists the 15 section and topic hubs that rawstory-headlines accepts. Each entry has a slug, a display name such as U.S. News or Raw Exclusives, and the hub page url. Hubs overlap: us-news, trump-news and smartnews share most recent stories, and presidential-campaign-issues is dormant.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and discloses meaningful behavior beyond the schema: exactly 15 entries, the returned fields (`slug`, `name`, `url`), overlapping hub content, and that `presidential-campaign-issues` is dormant. These details help an agent interpret results correctly.

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 front-loaded, moving quickly from purpose to count, returned fields, and edge cases. Every sentence adds useful information, and there is no filler.

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 zero-parameter list tool with no annotations or output schema, the description is unusually complete: it gives the count, entry shape, example names, overlap behavior, and a dormant-section caveat. An agent has enough context to call and interpret it correctly.

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?

The tool has zero input parameters, so the baseline is 4. The description does not need to explain parameters, and it appropriately focuses on the returned section metadata instead.

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 uses a specific verb and resource: 'Get Raw Story sections' and 'Lists the 15 section and topic hubs.' It also distinguishes this tool from the sibling `rawstory-headlines` by stating that these are the hubs that tool accepts, so an agent can tell why it exists separately.

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 clearly establishes context by saying the listed hubs are what `rawstory-headlines` accepts, which implies this is a discovery/lookup tool for valid section slugs. However, it does not explicitly state when not to use it or name a direct alternative beyond the consumer relationship.

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