Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sportskeeda_football_options

Discover football tournaments and matchday rounds. Omit event to list tournaments; provide event to retrieve all available matchday slugs for data feeds.

Instructions

Discover football tournaments and matchdays. Lists the live football widget's tournament selector. With event, follows the full previous/next matchday chain and returns every currently offered round slug. The discovered values feed sportskeeda-football-data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
eventNoLive tournament slug; current selector: featured, epl, uefa-champions-league, uefa-nations-league, la-liga, ligue-1, mls, bundesliga. Omit to list tournaments only

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 burden. It usefully discloses that supplying an event traverses the full previous/next matchday chain and returns every offered round slug, which is real behavioral detail. However, it says nothing about return shape, pagination, errors, or that feeding the downstream tool is the intended workflow beyond a passing mention.

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 sentences, front-loaded with the core purpose before the conditional drill-down. The "live football widget" phrasing adds site-specific jargon rather than clarity, but there is no wasted filler overall.

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?

Without an output schema the description must cover return values, and it does explain that tournaments or round slugs come back. The linkage to sportskeeda-football-data is stated but not elaborated into a concrete next-step workflow, leaving a minor gap for a discovery-oriented tool.

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% and the parameter description already enumerates the valid slugs (featured, epl, etc.), so the schema does the heavy lifting. The description only adds "omit to list tournaments only," which largely restates the schema. Baseline 3 is appropriate.

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 gives a specific verb+resource ("Discover football tournaments and matchdays") and explains the two-mode behavior of the tool. It also names the downstream sibling (sportskeeda-football-data) that consumes its output, which aids differentiation, though the phrase "live football widget's tournament selector" is jargon-laden.

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 states the conditional behavior clearly: omit the parameter to list tournaments only, supply it to follow the matchday chain. The note that discovered values feed sportskeeda-football-data implies this is a prerequisite discovery step, giving the agent usable context, though there is no explicit "do not use for X" 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