Football Data

Get Competition Standings

get_competition_standings

Read-onlyIdempotent

League table / standings for a competition season — 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. Returns total / home / away tables.

Input 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

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

B3.2/5.0

Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), so the description has a lower burden. It adds limited behavioral context by stating that total, home, and away tables are returned, but does not describe constraints like matchday snapshot behavior or pagination.

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 description is a single front-loaded sentence that states the core purpose immediately. The long list of competitions is relevant but somewhat dense, keeping it just below a perfect score.

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?

With rich annotations and an output schema present, the description provides enough context about what the tool returns and which competitions are supported. The main gap is the lack of explicit guidance on when to choose this tool over sibling match or competition-listing tools.

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 all three parameters. The description adds a list of supported competitions, which loosely maps to the competition parameter, but does not explain code formats or clarify season/matchday semantics 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 resource and scope: league table/standings for a competition season, with explicit return variants (total/home/away tables). It distinguishes itself implicitly from siblings like get_competition_matches and list_competitions, though it does not explicitly name those alternatives.

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

Usage Guidelines2/5

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

The description gives no explicit guidance on when to use this tool versus alternatives such as get_competition_matches or list_competitions. Usage is only implied by the resource name and competition list.

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.