Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

livescience_headlines

Fetch Live Science headlines for a chosen section, such as space, health, or technology, and get each article's title, URL, author, and publication time.

Instructions

Get Live Science section headlines. Returns current Live Science headlines for one section. section is required and takes one of 14 slugs: animals, archaeology, chemistry, features, health, human-behavior, interviews, news, opinion, physics-mathematics, planet-earth, products, space or technology. Each item has a title and URL, plus author, publication time and image when the section page shows them.

Input Schema

NameRequiredDescriptionDefault
sectionYesLive Science section slug

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 disclose the return shape (title and URL, plus author, publication time and image when shown). It omits pagination, result-count limits, and freshness guarantees, but the return-item disclosure is meaningful value with no output schema present.

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?

Front-loaded with the core purpose and return summary, then the enum list. Efficient overall, though the inline enumeration of all 14 slugs is somewhat redundant with the schema and lengthens the description.

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 covers purpose, the required parameter, and the shape of returned items, which is enough for correct invocation. Pagination/limits are the only notable omission.

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 single parameter is a fully enumerated slug, so the schema already documents it. The description restates the same 14 enum values rather than adding format or selection guidance, so it does not exceed the schema baseline.

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?

States a specific verb and resource ('Get Live Science section headlines') and scopes it to a single section, which is clear enough to separate it from livescience_article or livescience_author. It does not explicitly name a sibling to contrast against, so it falls just short of full differentiation.

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 resource name but there is no explicit when-to-use guidance or reference to alternatives such as livescience_news or livescience_article. The agent can infer the purpose but is given no routing rules or exclusions.

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