Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sportskeeda_football_data

Fetch football fixtures and standings from an event slug; add an optional matchday to target a specific round.

Instructions

Get football fixtures and standings. Returns first-party football widget fixtures and standings. Event and optional matchday must be offered by football-options. Omit matchday for the widget's selected round. Scores and standings reflect upstream data, which may be stale.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
eventYesTournament slug from football-options; current selector: featured, epl, uefa-champions-league, uefa-nations-league, la-liga, ligue-1, mls, bundesliga
matchdayNoRound slug from football-options for the selected event

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.7

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that data comes from an upstream source that "may be stale" and that several inputs are constrained to widget options, but it says nothing about return shape, pagination, or freshness timing beyond the vague staleness warning.

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?

Four short sentences, front-loaded with the purpose. The second sentence largely restates the first with the "first-party widget" qualifier, a small redundancy, but the usage constraints are laid out efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read tool with no output schema, the description covers source, prerequisite, and a staleness caveat but never characterizes what the fixtures/standings response contains or how it is scoped by round, leaving some gaps an agent must infer.

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 schema already documents both slugs, so the baseline is 3. The description adds minor meaning by stating both values must originate from football-options and that matchday defaults to the widget's selected round, but gives no format detail beyond the schema.

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 two resources ("Get football fixtures and standings") and identifies the data source ("first-party football widget fixtures and standings"). It contrasts implicitly with siblings like sportskeeda_standings by covering both fixtures and standings, but does not explicitly name a sibling tool to differentiate from.

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?

It gives the prerequisite that "Event and optional matchday must be offered by football-options," routing the agent to the sibling that supplies valid slugs, and clarifies "Omit matchday for the widget's selected round." There is no explicit when-not to use it versus other football tools, but the context is clear.

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