footballcharts-mcp

Match results

get_results

Read-onlyIdempotent

Returns the finished matches of one league season in chronological order: date, teams, full-time and half-time score, first-goal minute and a goalless flag. team keeps the matches where either side's name contains the given text (case-insensitive); last=N keeps only the N most recent matches. Contains no odds.

Input Schema

Name	Required	Description
`last`	No	Keep only the N latest matches of the season, e.g. 5 for recent form (default: all)
`team`	No	Team name substring, e.g. 'Liverpool'
`league`	Yes	League key as listed by list_leagues, e.g. 'premier' (England), 'spain1', 'brazil1', 'sweden1', 'wgermany1' (women). Not the display name.
`season`	No	Season string as listed by list_leagues: '2026-2027' for winter-calendar leagues, '2026' for summer-calendar leagues (Brazil, Sweden, Norway, Japan…). Omit for the current season. The free tier serves the current and previous season.

Output Schema

Name	Required	Description
`note`	No
`count`	No
`league`	No
`season`	No
`matches`	No
`attribution`	No	Cite as "Data by football-charts.com"
`season_state`	No	'in_season' or 'finished'
`current_season`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 16, 2026

removedOutput schema / properties / current_season / $ref
```
Removed value: -"#/properties/league"
```

changedOutput schema / properties / matches / anyOf

Previous value: -[
-  {
-    "items": {
-      "additionalProperties": true,
-      "properties": {
-        "awayTeam": {
-          "type": "string"
-        },
-        "date": {
-          "$ref": "#/properties/league"
-        },
-        "first_goal_time": {
-          "$ref": "#/properties/count",
-          "description": "Minute of the first goal; null when goalless"
-        },
-        "first_goal_time_extra": {
-          "$ref": "#/properties/count",
-          "description": "Stoppage-time minutes added to first_goal_time"
-        },
-        "goalless": {
-          "type": [
-            "boolean",
-            "null"
-          ]
-        },
-        "homeTeam": {
-          "type": "string"
-        },
-        "ht_result": {
-          "$ref": "#/properties/league",
-          "description": "Half-time 'home:away'"
-        },
-        "score": {
-          "$ref": "#/properties/league",
-          "description": "Full-time 'home:away', e.g. '3:0'"
-        },
-        "time": {
-          "$ref": "#/properties/league"
-        }
-      },
-      "required": [
-        "homeTeam",
-        "awayTeam"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "additionalProperties": true,
+      "properties": {
+        "awayTeam": {
+          "type": "string"
+        },
+        "date": {},
+        "first_goal_time": {
+          "description": "Minute of the first goal; null when goalless"
+        },
+        "first_goal_time_extra": {
+          "description": "Stoppage-time minutes added to first_goal_time"
+        },
+        "goalless": {
+          "type": [
+            "boolean",
+            "null"
+          ]
+        },
+        "homeTeam": {
+          "type": "string"
+        },
+        "ht_result": {
+          "description": "Half-time 'home:away'"
+        },
+        "score": {
+          "description": "Full-time 'home:away', e.g. '3:0'"
+        },
+        "time": {}
+      },
+      "required": [
+        "homeTeam",
+        "awayTeam"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / note / $ref
```
Removed value: -"#/properties/league"
```
removedOutput schema / properties / season / $ref
```
Removed value: -"#/properties/league"
```
removedOutput schema / properties / season_state / $ref
```
Removed value: -"#/properties/league"
```

Changed2 schema fields changedOct 9, 2026

changedInput schema / properties / league / description

Previous value: -"League key from list_leagues, e.g. 'premier' (England), 'spain1', 'brazil1', 'sweden1', 'wgermany1' (women). Not the display name."New value: +"League key as listed by list_leagues, e.g. 'premier' (England), 'spain1', 'brazil1', 'sweden1', 'wgermany1' (women). Not the display name."

changedInput schema / properties / season / description

Previous value: -"Season string exactly as list_leagues returns it: winter-calendar leagues look like '2026-2027', summer-calendar leagues (Brazil, Sweden, Norway, Japan…) like '2026'. Omit for the current season. The free tier serves the current and previous season only."New value: +"Season string as listed by list_leagues: '2026-2027' for winter-calendar leagues, '2026' for summer-calendar leagues (Brazil, Sweden, Norway, Japan…). Omit for the current season. The free tier serves the current and previous season."

Changed7 schema fields changedSep 6, 2026

addedInput schema / properties / last / anyOf

Added value: +[
+  {
+    "maximum": 500,
+    "minimum": 1,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / last / description

Previous value: -"Return only the N most recent matches (default: all)"New value: +"Keep only the N latest matches of the season, e.g. 5 for recent form (default: all)"

removedInput schema / properties / last / maximum
```
Removed value: -500
```
removedInput schema / properties / last / minimum
```
Removed value: -1
```
removedInput schema / properties / last / type
```
Removed value: -"integer"
```

changedInput schema / properties / team / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "attribution": {
+      "description": "Cite as \"Data by football-charts.com\"",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "count": {},
+    "current_season": {
+      "$ref": "#/properties/league"
+    },
+    "league": {},
+    "matches": {
+      "anyOf": [
+        {
+          "items": {
+            "additionalProperties": true,
+            "properties": {
+              "awayTeam": {
+                "type": "string"
+              },
+              "date": {
+                "$ref": "#/properties/league"
+              },
+              "first_goal_time": {
+                "$ref": "#/properties/count",
+                "description": "Minute of the first goal; null when goalless"
+              },
+              "first_goal_time_extra": {
+                "$ref": "#/properties/count",
+                "description": "Stoppage-time minutes added to first_goal_time"
+              },
+              "goalless": {
+                "type": [
+                  "boolean",
+                  "null"
+                ]
+              },
+              "homeTeam": {
+                "type": "string"
+              },
+              "ht_result": {
+                "$ref": "#/properties/league",
+                "description": "Half-time 'home:away'"
+              },
+              "score": {
+                "$ref": "#/properties/league",
+                "description": "Full-time 'home:away', e.g. '3:0'"
+              },
+              "time": {
+                "$ref": "#/properties/league"
+              }
+            },
+            "required": [
+              "homeTeam",
+              "awayTeam"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "note": {
+      "$ref": "#/properties/league"
+    },
+    "season": {
+      "$ref": "#/properties/league"
+    },
+    "season_state": {
+      "$ref": "#/properties/league",
+      "description": "'in_season' or 'finished'"
+    }
+  },
+  "type": "object"
+}

First observedSep 6, 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, destructiveHint=false and openWorldHint, so safety is covered. The description adds genuinely new behavioral facts: results are ordered chronologically, team matching is case-insensitive and applies to either side, and odds are absent from the payload.

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?

Three dense sentences with the primary purpose front-loaded, then filter semantics, then the exclusion. No filler or redundant restatement of the tool name.

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 list tool with a rich schema (100% coverage, output schema present) and full annotations, the description covers scope, ordering, filtering and content exclusions adequately. Data-availability limits (free tier, season default) live in the schema rather than the description, so nothing essential is missing, though the description could have surfaced the current/previous-season constraint.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real semantics beyond the schema: 'team' matches either side's name (not just one) and the match is case-insensitive, which the schema's 'Team name substring' does not convey. It restates 'last=N' semantics already present in the schema, so it is not a 5.

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 with scope: 'Returns the finished matches of one league season in chronological order', then enumerates the returned fields. The 'finished matches' scope cleanly separates it from get_fixtures (scheduled) and get_match (single match) without needing to name 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?

Gives clear context for how the filters are meant to be used ('team keeps matches where either side's name contains the text', 'last=N keeps only the N most recent') and an explicit exclusion ('Contains no odds'), which steers the agent away from this tool for betting data. It stops short of naming an alternative tool or stating when-not-to-use beyond the odds exclusion.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All footballcharts-mcp 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.