Skip to main content
Glama

Football Data

Get Competition Matches

get_competition_matches
Read-onlyIdempotent

Fixtures and results for a competition, Premier League, Championship, Primera División/La Liga, Serie A, Bundesliga, Ligue 1, Eredivisie, Primeira Liga, Brasileirão, Copa Libertadores, UEFA Champions League, European Championship, or the World Cup (see competition codes below). Filter by status (SCHEDULED, LIVE, IN_PLAY, PAUSED, FINISHED, POSTPONED, SUSPENDED, CANCELLED), date range, matchday, stage, or season year. "Next round" / "upcoming fixtures" questions: pass no status or status: "SCHEDULED", not a matchday number, unless the caller already knows which matchday number it is.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "competition": "PL"
    },
    "name": "get_competition_matches"
  }
}

Input Schema

NameRequiredDescriptionDefault
stageNoStage (e.g., "GROUP_STAGE", "QUARTER_FINALS")
seasonNoSeason start year (e.g., 2025)
statusNoMatch status filter (SCHEDULED | LIVE | IN_PLAY | PAUSED | FINISHED | POSTPONED | SUSPENDED | CANCELLED)
date_toNoYYYY-MM-DD
matchdayNoRound number
date_fromNoYYYY-MM-DD
competitionYesCompetition code (e.g., "PL" = Premier League, "PD" = La Liga, "CL" = Champions League)

Output Schema

NameRequiredDescriptionDefault
countYesNumber of matches returned
matchesYes
competitionYesCompetition code used in the query

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "competition": "PL"
      +  },
      +  {
      +    "competition": "CL",
      +    "season": 2024,
      +    "status": "FINISHED"
      +  }
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "competition": {
      +      "description": "Competition code used in the query",
      +      "type": "string"
      +    },
      +    "count": {
      +      "description": "Number of matches returned",
      +      "type": "number"
      +    },
      +    "matches": {
      +      "items": {
      +        "properties": {
      +          "away": {
      +            "description": "Away team name",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "away_id": {
      +            "description": "Away team ID",
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "competition": {
      +            "description": "Competition name",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "competition_code": {
      +            "description": "Competition code",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "group": {
      +            "description": "Group name if applicable",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "home": {
      +            "description": "Home team name",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "home_id": {
      +            "description": "Home team ID",
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "id": {
      +            "description": "Match ID",
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "matchday": {
      +            "description": "Round/matchday number",
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "score_full_time": {
      +            "description": "Full-time score (e.g., '2-1' or '-' if not final)",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "score_half_time": {
      +            "description": "Half-time score (e.g., '1-0' or '-' if not played)",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "stage": {
      +            "description": "Competition stage (e.g., GROUP_STAGE)",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "status": {
      +            "description": "Match status",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "utc_date": {
      +            "description": "Match date/time in UTC (ISO 8601)",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "venue": {
      +            "description": "Venue name",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "winner": {
      +            "description": "Winner ('HOME', 'AWAY', 'DRAW', or null)",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "competition",
      +    "count",
      +    "matches"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world, non-destructive behavior. The description adds non-obvious query behavior, especially the rule for retrieving upcoming fixtures without a matchday. It does not discuss pagination or result limits, but the output schema likely covers return shape.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded, and the final sentence provides useful usage guidance. However, the long enumeration of competitions is verbose, and the phrase 'see `competition` codes below' is dangling because no codes appear below. A shorter reference to the schema would be cleaner.

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?

For a read-only competition match query with an output schema, full parameter documentation, and annotations, the description is largely complete. It covers filters, supported statuses, and the important upcoming-fixtures case. Minor gaps like pagination or timezone handling are not critical given the output schema.

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 explains each parameter. The description restates filter categories and lists competition names, but it says 'see competition codes below' without actually providing a code list. It adds only marginal meaning 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 clearly states the verb and resource: 'Fixtures and results for a competition.' It enumerates supported competitions, making the scope concrete. Sibling differentiation is implied by the competition focus, but no alternative tool is explicitly named or contrasted.

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 explicit guidance for 'next round' and 'upcoming fixtures' questions, specifying to omit status or use SCHEDULED rather than a matchday number. This is a useful when-to-use rule. However, it does not state when not to use this tool versus alternatives such as get_team_matches.

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.