Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sciencealert_article

Fetch article content from ScienceAlert by canonical URL to get title, authors, timestamps, image, cleaned paragraphs, and paywall status; section and author listing URLs are rejected.

Instructions

Get ScienceAlert article content. Returns a ScienceAlert article by absolute canonical url: title, description, section, authors, publication and update times, image, the cleaned body paragraphs and a paywalled flag. Section pages and author listing URLs are rejected.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesCanonical ScienceAlert article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.7

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and discloses the returned fields, including cleaned body paragraphs and a paywalled flag. It also states the URL validation behavior by rejecting non-article URLs, though it does not discuss permissions, rate limits, or error responses beyond rejection.

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?

Two sentences, front-loaded with the tool's purpose, followed by return contents and input constraints. There is no filler, and each sentence 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 simple one-parameter article-fetch tool with no output schema, the description is complete enough: it identifies the required URL type, lists the returned article fields, and states which URL types are rejected.

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%, so the baseline is 3. The description adds meaning beyond the schema by specifying that the url must be absolute and canonical, and by clarifying that section and author listing URLs are invalid inputs.

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 ScienceAlert article content' and 'Returns a ScienceAlert article'. It also distinguishes this article-detail tool from section pages and author listing pages, which it says are rejected.

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 says the tool requires an absolute canonical URL and explicitly rejects section pages and author listing URLs, giving useful when-not-to-use guidance. It does not explicitly name sibling tools such as sciencealert_headlines or sciencealert_sections as alternatives for discovery.

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