Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sciencealert_headlines

Fetch section headlines from ScienceAlert by choosing a category like space, health, tech or nature, and get each story's title and URL.

Instructions

Get ScienceAlert section headlines. Returns the latest ScienceAlert stories for one section. section is required and takes space, health, environment, humans, tech, nature, physics or this-week-in-science; other values are rejected. Each item has its title and URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sectionYesSection slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.7

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully states that results are the latest stories for one section, that each item contains a title and URL, and that invalid section values are rejected, but it omits pagination, result-count limits, and other behavioral details.

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?

The definition is front-loaded and efficient, starting with the core purpose and then covering required input and return shape. The enum list duplicates the schema slightly, but it remains compact and scannable.

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?

For a simple one-parameter headline tool with no output schema, the description provides enough context: it explains the required section, enumerates valid values, and describes returned item fields. Minor gaps around sibling differentiation and pagination keep it from being fully complete.

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 description coverage is 100%, so the enum and required constraint are already documented. The description repeats the valid section values and adds that other values are rejected, but it does not greatly extend parameter semantics 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 uses a specific verb and resource: getting ScienceAlert section headlines and returning the latest stories for one section. It clearly identifies the scope, though it does not explicitly distinguish this from the closely related sciencealert_news sibling.

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 required `section` parameter and its enumerated values. However, the description does not explicitly say when to use this tool instead of sciencealert_news, sciencealert_sections, or sciencealert_article, leaving sibling routing to inference.

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