Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

livescience_news

Fetch Live Science top stories with titles, URLs, summaries, authors, publication times, and images. Use it to track current science news across the site. Narrow by section with livescience-headlines.

Instructions

Get Live Science top stories. Returns Live Science's current top stories across the site, with no parameters. Each item has its title, URL, summary, author, publication time and image where available. Use livescience-headlines to narrow to one section.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

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 burden and does state key traits: it returns current top stories, takes no parameters, and lists the exact fields returned (title, URL, summary, author, publication time, image). It does not explicitly note read-only behavior, but 'Get' and a news feed imply a safe read. The return structure disclosure is a solid addition beyond structured fields.

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 description is front-loaded and appropriately sized, but there is slight redundancy between 'Get Live Science top stories' and 'Returns Live Science's current top stories across the site.' Every sentence earns its place otherwise.

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?

Given the simple no-param feed, no annotations, and no output schema, the description covers the essentials: what it returns, the fields per item, and the alternative tool. It omits minor details like number of stories or update frequency, but these are not critical for correct invocation.

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 parameters and the schema description coverage is 100%, so the baseline is 4. The description reinforces this by saying 'with no parameters,' which is consistent and leaves no ambiguity.

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 states a specific verb and resource: 'Get Live Science top stories.' It also clarifies scope ('across the site') and explicitly names the sibling tool to use when narrowing to a section. An agent can distinguish this from livescience_headlines without opening the schema.

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?

The description gives an explicit alternative: 'Use `livescience-headlines` to narrow to one section.' This names the condition that selects the other tool and makes the routing decision clear. Although it doesn't mention livescience_article, the primary alternative is covered.

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