Skip to main content
Glama

sportskeeda_football_data

Read-only

Get Sportskeeda football matches, scores, and standings rows for an event slug and optional matchday discovered with sportskeeda_football_options.

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": {
      "event": "<event>"
    },
    "name": "sportskeeda_football_data"
  }
}

Input 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

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / event / description
      Added value: +"Tournament slug from football-options; current selector: featured, epl, uefa-champions-league, uefa-nations-league, la-liga, ligue-1, mls, bundesliga"
    • addedInput schema / properties / matchday / description
      Added value: +"Round slug from football-options for the selected event"
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds that this is a data-retrieval tool (matches, scores, standings rows), but discloses nothing about pagination, auth requirements, or freshness. Given the lower bar set by annotations, this is adequate but thin.

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?

A single sentence, front-loaded with the verb and resource, with the dependency on football_options trailing it. No filler or repetition.

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?

An output schema exists, so return values need no explanation, and both parameters are fully documented in the schema. The description supplies the discovery workflow, which is the main missing piece. Only marginal gaps (no note on scope or filtering behavior) remain.

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%, so the schema already documents both 'event' and 'matchday' fully, including the event slug list. The description only echoes that matchday is optional and that slugs come from football_options; it adds no format or syntax detail 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 ('Get') and the exact resource: Sportskeeda football matches, scores, and standings rows. It clearly differentiates from the sibling sportskeeda_football_options by positioning that tool as the discovery step, though it does not distinguish itself from other sportskeeda football-adjacent tools like sportskeeda_schedule or sportskeeda_standings.

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 description establishes a prerequisite workflow: the event slug (and optional matchday) should be 'discovered with sportskeeda_football_options.' That tells the agent when to reach for the sibling first. It stops short of explicit when-not-to-use guidance, so not a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.