Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

skysports_headlines

Retrieve article cards and headlines from a specified Sky Sports section listing page using a required section slug; returns the first listing page.

Instructions

Get Sky Sports section headlines. Returns the article cards from one Sky Sports section listing page. section is required and takes one of 22 slugs such as football, f1, cricket, rugby-union, golf, boxing, nfl or darts. The site's Show More pagination is not exposed, so only the first listing comes back.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "section": "<section>"
    },
    "name": "skysports_headlines"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectionYesSky Sports section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.7

TDQS

A3.8/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses a concrete, non-obvious limitation — 'the site's Show More pagination is not exposed, so only the first listing comes back' — which tells the agent it cannot page deeper and must not retry expecting more. Auth, rate limits and freshness are not covered, keeping it below 5.

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?

Three sentences, front-loaded with what is returned, then the required parameter, then the pagination caveat. No filler and nothing repeated; the most consequential constraint is placed last but still within a compact block.

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?

There is no output schema, so the description must characterize the return value; 'article cards from one Sky Sports section listing page' plus the pagination limit covers the essentials. It stops short of describing the fields of an article card or whether the result is empty for sparse sections, which would fully close the gap.

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 coverage is 100%: the single `section` parameter is documented and its 22-value enum is fully enumerated in the schema. The description restates the count ('one of 22 slugs') and gives examples already present in the enum, so it adds little beyond the schema. Baseline 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?

States a specific verb and resource ('Get Sky Sports section headlines') and narrows the scope to 'the article cards from one Sky Sports section listing page', which separates it from a generic news feed. It does not explicitly name or contrast with the sibling tools skysports_news, skysports_sections or skysports_article, so an agent must infer the boundary.

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 tells the agent that `section` is required and enumerates the valid slug family, which implies when the tool is callable. It never states when to prefer this over skysports_news or skysports_article, nor any exclusions, so usage is only implied rather than guided.

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