Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

livescience_article

Fetch a Live Science article by its canonical URL to return structured title, description, section, authors, images, timestamps, paragraphs, and paywall status.

Instructions

Get Live Science article content. Returns a Live Science article by url, a canonical HTTPS livescience.com article link. The response has the title, description, section, authors, lead image, publish and update times, body paragraphs and a paywalled flag.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Live Science article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does meaningful work: it enumerates the returned fields (title, description, section, authors, lead image, publish/update times, body paragraphs) and flags a `paywalled` field, which is valuable behavioral context. It does not mention auth or rate limits, but for a public read endpoint the disclosure of the paywall flag and payload shape is substantive.

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?

Two sentences with no filler, front-loading the action ('Get Live Science article content') before the input and return details. Efficient and well-ordered, though the second sentence is a fairly dense enumeration.

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 one-parameter, no-output-schema tool, the description compensates by describing the response payload and the paywalled flag, which is exactly the information an agent needs. Nothing critical is missing, though input format nuances (trailing slashes, non-canonical URLs) go unaddressed.

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% and the schema already documents the single `url` parameter as 'Canonical Live Science article URL'. The description restates this as 'a canonical HTTPS `livescience.com` article link', adding only marginal format detail, so the baseline of 3 applies.

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 states a specific verb and resource: 'Get Live Science article content' and 'Returns a Live Science article by `url`'. This clearly distinguishes a single-article fetch from the sibling listing tools (livescience_headlines, livescience_news, livescience_sections), though it never names them explicitly.

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 only implied: the tool needs a canonical article URL, so an agent infers it is used once a URL is known. There is no explicit statement of when to use this versus livescience_headlines or livescience_news, and no guidance on where the URL comes from.

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