Football Data

Get Competition Standings

get_competition_standings

Read-onlyIdempotent

League table for a competition season. Returns total / home / away tables.

Input Schema

TableJSON Schema

Name	Required	Description
`season`	No	Season start year (optional, defaults current)
`matchday`	No	Standings as of a specific matchday (optional)
`competition`	Yes	Competition code

Output Schema

TableJSON Schema

Name	Required	Description	Default
`standings`	Yes
`competition`	Yes	Competition name or code

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "competition": "PL"
+  },
+  {
+    "competition": "PD",
+    "matchday": 10,
+    "season": 2024
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "competition": {
+      "description": "Competition name or code",
+      "type": "string"
+    },
+    "standings": {
+      "items": {
+        "properties": {
+          "group": {
+            "description": "Group name if applicable",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "stage": {
+            "description": "Stage name (e.g., FINAL_STANDINGS)",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "table": {
+            "items": {
+              "properties": {
+                "draw": {
+                  "description": "Games drawn",
+                  "type": [
+                    "number",
+                    "null"
+                  ]
+                },
+                "form": {
+                  "description": "Recent form (W/D/L sequence)",
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                },
+                "ga": {
+                  "description": "Goals against",
+                  "type": [
+                    "number",
+                    "null"
+                  ]
+                },
+                "gd": {
+                  "description": "Goal difference",
+                  "type": [
+                    "number",
+                    "null"
+                  ]
+                },
+                "gf": {
+                  "description": "Goals for",
+                  "type": [
+                    "number",
+                    "null"
+                  ]
+                },
+                "lost": {
+                  "description": "Games lost",
+                  "type": [
+                    "number",
+                    "null"
+                  ]
+                },
+                "played": {
+                  "description": "Games played",
+                  "type": [
+                    "number",
+                    "null"
+                  ]
+                },
+                "points": {
+                  "description": "Total points",
+                  "type": [
+                    "number",
+                    "null"
+                  ]
+                },
+                "position": {
+                  "description": "Table position",
+                  "type": [
+                    "number",
+                    "null"
+                  ]
+                },
+                "team": {
+                  "description": "Team name",
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                },
+                "team_id": {
+                  "description": "Team ID",
+                  "type": [
+                    "number",
+                    "null"
+                  ]
+                },
+                "won": {
+                  "description": "Games won",
+                  "type": [
+                    "number",
+                    "null"
+                  ]
+                }
+              },
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "type": {
+            "description": "Standings type (TOTAL, HOME, AWAY)",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "competition",
+    "standings"
+  ],
+  "type": "object"
+}

First observedMay 12, 2026

TDQS

A4/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. The description adds behavioral insight: it returns three tables (total, home, away), which is beyond what annotations provide. No contradictions.

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?

Two short, focused sentences with no extraneous information. Front-loaded with the core purpose. Every sentence earns its place.

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?

Given the presence of an output schema (not shown) and rich annotations, the description is complete enough. It explains the output breakdown and tool purpose. Could mention supported competition codes or season range, but not necessary.

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 baseline is 3. The description does not add any parameter-specific meaning beyond what the schema already defines. No additional context for parameters is provided.

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?

The description clearly states the tool returns a league table for a competition season with total, home, and away breakdowns. This distinguishes it from sibling tools like get_competition_matches (matches) and list_competitions (list of competitions).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for retrieving standings but does not explicitly state when to use this tool over alternatives, nor does it provide exclusions or prerequisites. The context is clear but lacks guidance on sibling tools.

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.