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.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`count`	Yes	Total number of competitions
`competitions`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 22, 2026

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"
+}

First observedMay 12, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds non-obvious behavior beyond that: results are scoped to 'competitions accessible on your plan', and each entry carries `current_matchday` for its live season — both facts an agent cannot derive from the annotation block.

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-code instruction are front-loaded, and the long competition enumeration functions as a controlled vocabulary rather than filler. It is dense but every clause (code list, code usage, current_matchday) carries information the agent needs.

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 listing tool with a full output schema and strong annotations, the description supplies everything else that matters: what is listed, the plan-based scoping, the returned identifiers, and how to use them downstream. Nothing needed to call it correctly is missing.

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 the baseline is 4 and there is nothing for the description to compensate for. It uses the space instead to document the shape of returned fields (`code`, `current_matchday`), which is useful but overlaps the existing output schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List competitions') and immediately bounds the resource by enumerating exactly which competitions are returned, including their codes. An agent can tell this apart from get_competition_matches or get_competition_standings, which operate on a single competition rather than enumerating them.

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 sentence 'Use the returned `code` for downstream calls' positions this tool as the discovery entry point feeding the competition-scoped siblings, which is real routing guidance. It does not, however, explicitly say when NOT to use it or name the downstream tools it precedes, so it stops 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.

All Football Data tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.