Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

skysports_sections

List valid Sky Sports section slugs, names, and URLs accepted by the headlines lookup, covering football, F1, WWE, and Olympics.

Instructions

Get Sky Sports sections. Lists the 22 Sky Sports sections that skysports-headlines accepts, from football and f1 to wwe and olympics. Each entry has a slug, a display name and the section url. Winter Sports and Commonwealth Games pages returned 404 in the 2026-09-28 check and are not accepted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.7

TDQS

A4.4/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 burden, and it does substantial work: it discloses the cardinality (22 sections), the exact fields returned per entry (`slug`, `name`, `url`), and a real-world data caveat (Winter Sports and Commonwealth Games 404'd on a specific date and are excluded). That is useful behavioral context beyond a bare name restatement, though it does not cover response format or ordering.

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 tight sentences, front-loaded with the purpose and then the payload details. The dated 404 caveat is the one slightly verbose element, but it earns its place by telling the agent which slugs are unusable.

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, but the description compensates by describing the entry fields, the total count, and the excluded sections. For a parameterless listing tool this is complete enough to call and interpret 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?

The tool takes zero parameters, so the baseline is 4. The description correctly implies there is nothing to supply; the only inputs are the section slugs being described as outputs.

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 and resource ("Get Sky Sports sections") and immediately distinguishes itself from the sibling skysports_headlines by explaining that this is the enumeration of slugs that headlines accepts. An agent can tell what it does and how it relates to the sibling 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The link to `skysports-headlines` establishes a clear routing relationship: call this to discover valid section slugs for that tool. It stops short of an explicit when/when-not statement or naming any other alternative, so it is strong context rather than full guidance.

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