Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sciencealert_news

Retrieve ScienceAlert top stories from across the site as structured JSON, including titles, URLs, summaries, authors, and publication times. Use it to track current science news without parameters.

Instructions

Get ScienceAlert top stories. Returns ScienceAlert's latest top stories across the site. Takes no parameters, and sciencealert-headlines narrows by section instead. Each item has its title, URL, summary, author and publication time.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sciencealert_news"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.7

TDQS

A4.6/5.0
Behavior4/5

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

No annotations are provided, but the description discloses that the operation is parameterless and read-oriented by describing the returned item fields (title, URL, summary, author, publication time). It doesn't mention result volume, pagination, or rate limits, but those are minor for a simple read operation.

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?

Three tight sentences: purpose first, sibling distinction second, return shape third. Nothing is redundant or front-loaded poorly.

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?

With no output schema, the description usefully enumerates the fields of each returned item and explains the no-parameter behavior. It lacks details like item count or pagination, but is otherwise sufficient for this straightforward read tool.

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?

There are zero parameters, so the baseline is 4. The description correctly states 'Takes no parameters,' which fully covers the invocation surface.

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 and resource ('Get ScienceAlert top stories'), clarifies scope ('across the site'), and explicitly distinguishes it from `sciencealert-headlines`, which narrows by section.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use this tool versus the sibling: use this for site-wide top stories, use `sciencealert-headlines` for section-level filtering. Takes no parameters, so no additional invocation guidance is needed.

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