Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sun_article

Fetches The Sun article content from a canonical HTTPS URL, returning title, section, authors, timestamps, lead image, paragraphs, and paywall status; subscriber-only pages return an error.

Instructions

Get The Sun article content. Returns one The Sun article by url, a canonical HTTPS article link. The response has the title, description, section, authors, publication and update times, lead image URL, body paragraphs and a paywalled flag. Subscriber-only or blocked pages return an error instead.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical The Sun article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4/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 behavioral burden and does well: it enumerates the returned payload (title, description, section, authors, times, image, paragraphs, paywalled flag) and discloses error behavior for subscriber-only or blocked pages. It does not mention auth requirements, rate limits, or any failure mode beyond the paywall case.

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?

Three front-loaded sentences: what it does, what comes back, and the failure case. Efficient, though 'The Sun article' is repeated in the first two sentences where a pronoun would suffice.

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?

No output schema and no annotations exist, so the description must carry the return-value burden alone – and it enumerates the payload fields thoroughly while also covering the blocked/paywalled error path. Nothing essential for calling the tool correctly is missing.

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 only one parameter exists, so the schema already documents `url`. The description restates it as a 'canonical HTTPS article link', adding the HTTPS constraint and matching the tool's single-parameter contract, but no syntax or format detail beyond the schema. Baseline 3 applies.

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 (Get) and resource (The Sun article content), and clarifies it returns exactly one article keyed by `url`. This distinguishes it from siblings like sun_headlines, sun_news, and sun_sections, which list rather than fetch a single article.

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?

The description implies usage by explaining the tool takes 'a canonical HTTPS article link', but never states when to choose it over sun_headlines or sun_news (e.g., that you first need a URL from a listing tool). No explicit when-to-use or when-not-to-use guidance is given.

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