Skip to main content
Glama

Football Data

List Competitions

list_competitions
Read-onlyIdempotent

List competitions accessible on your plan, Premier League (PL), Championship (ELC), Primera División/La Liga (PD), Serie A (SA), Bundesliga (BL1), Ligue 1 (FL1), Eredivisie (DED), Primeira Liga (PPL), Campeonato Brasileiro Série A / Brasileirão (BSA), Copa Libertadores (CLI), UEFA Champions League (CL), European Championship (EC), FIFA World Cup (WC). Use the returned code for downstream calls. Each entry includes current_matchday for its live season.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
countYesTotal number of competitions
competitionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {}
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "competitions": {
      +      "items": {
      +        "properties": {
      +          "area": {
      +            "description": "Geographic area name",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "code": {
      +            "description": "Competition code (e.g., PL, PD, CL)",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "current_matchday": {
      +            "description": "Current matchday number",
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "current_season_end": {
      +            "description": "Current season end date (YYYY-MM-DD)",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "current_season_start": {
      +            "description": "Current season start date (YYYY-MM-DD)",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "emblem": {
      +            "description": "Competition emblem URL",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "id": {
      +            "description": "Competition ID",
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "name": {
      +            "description": "Competition name",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "plan": {
      +            "description": "Availability plan tier",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "type": {
      +            "description": "Competition type",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "count": {
      +      "description": "Total number of competitions",
      +      "type": "number"
      +    }
      +  },
      +  "required": [
      +    "count",
      +    "competitions"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds two things beyond that: results are scoped to the caller's plan, and each entry carries `current_matchday` for its live season. It stops short of disclosing ordering, caching, or whether the catalog varies by season, so the added context is modest.

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?

The purpose and the downstream-use instruction are front-loaded, and the two closing sentences about `code` and `current_matchday` are high value. The long inline enumeration of league codes is bulky and partly redundant with the tool's own output, which keeps it from a 5.

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?

For a zero-parameter, read-only catalog tool with an output schema, nothing an agent needs is missing: it knows what is returned, that results are plan-scoped, and how to use the codes downstream. The output schema carries the structural detail, so no return-format prose is required.

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 there is no parameter meaning to convey; baseline for a 0-param tool is 4. The description usefully documents the return-field semantics (`code` as a downstream key, `current_matchday` as season state) instead.

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 opens with a specific verb and resource ("List competitions accessible on your plan") and enumerates the exact competition codes returned, so an agent knows precisely what comes back. It does not explicitly name which sibling consumes those codes, leaving differentiation from get_competition_matches/get_competition_standings implicit rather than stated.

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?

"Use the returned `code` for downstream calls" establishes a clear call-order workflow: fetch this first, then pass codes into competition-scoped tools. There is no explicit when-not guidance or named alternative, so it falls short of full when/when-not coverage.

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.