Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

skysports_article

Fetch structured Sky Sports article data from a URL, returning title, description, authors, timestamps, image, and body paragraphs.

Instructions

Get a Sky Sports article. Returns a Sky Sports article by url, an HTTPS skysports.com address with a sport news path such as /football/news/<id>/<slug>: title, description, section, authors, publication and update times, image and body paragraphs. The returned URL uses www.skysports.com, and query strings and fragments are discarded.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesCanonical Sky Sports article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.7

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 transparency burden and does well: it discloses the returned fields and explains URL normalization (returned URL uses `www.skysports.com`, query strings and fragments are discarded). It does not cover error behavior or redirect handling, but for a read-only article fetcher this is largely adequate.

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 purpose and immediately followed by return-value details and URL normalization rules. There is no filler, and every sentence provides useful information for calling the tool.

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?

There is no output schema, so the description must explain return values, which it does by listing title, description, section, authors, publication/update times, image, and body paragraphs. Combined with the URL format guidance and canonicalization behavior, the definition gives an agent enough context to invoke it correctly.

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 already 100%, so the baseline is 3, but the description adds meaningful parameter context beyond the schema: an example `/football/news/<id>/<slug>` path and the fact that query strings and fragments are discarded. It effectively explains what a valid input URL looks like and how it will be normalized.

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 a Sky Sports article') and identifies the lookup key ('by `url`'). It is clear that this is an article-detail tool rather than a list tool, but it does not explicitly differentiate itself from siblings such as `skysports_headlines`, `skysports_news`, or `skysports_sections`.

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: the tool requires a Sky Sports article URL, and the description gives the expected path shape. However, it offers no explicit guidance on when to choose this tool over sibling tools like headlines, news, or sections, so selection guidance remains inferential.

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