footballcharts-mcp

Goal timing

get_goal_timing

Read-onlyIdempotent

Returns goals per 15-minute period (0-15 to 90+) for every team in one league season, with each team's peak period or periods (ties are listed together), share of late goals and share of first-half goals, plus league totals and the league's most active period. team limits the result to teams whose name contains the given text.

Input Schema

Name	Required	Description
`team`	No	Team name substring, e.g. 'Flamengo' — returns that team's row only
`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
`data`	No
`note`	No
`stats`	No
`league`	No
`season`	No
`time_bins`	No
`attribution`	No	Cite as "Data by football-charts.com"
`team_filter`	No
`team_not_found`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 16, 2026

changedOutput schema / properties / data / anyOf

Previous value: -[
-  {
-    "items": {
-      "additionalProperties": true,
-      "properties": {
-        "bins": {
-          "anyOf": [
-            {
-              "additionalProperties": {
-                "type": "number"
-              },
-              "type": "object"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "description": "Goals per bin: '0-15','15-30','30-45','45+','46-60','60-75','75-90','90+'"
-        },
-        "first_half_pct": {
-          "$ref": "#/properties/data/anyOf/0/items/properties/late_share_pct"
-        },
-        "late_share_pct": {
-          "description": "% of goals from 75′ on"
-        },
-        "peak_bins": {
-          "anyOf": [
-            {
-              "items": {
-                "type": "string"
-              },
-              "type": "array"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "description": "Bin(s) with most goals — ties are listed; report a tie as a tie"
-        },
-        "peak_goals": {
-          "$ref": "#/properties/stats/anyOf/0/properties/total_goals"
-        },
-        "team": {
-          "type": "string"
-        },
-        "total": {
-          "$ref": "#/properties/stats/anyOf/0/properties/total_goals"
-        }
-      },
-      "required": [
-        "team"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "additionalProperties": true,
+      "properties": {
+        "bins": {
+          "anyOf": [
+            {
+              "additionalProperties": {
+                "type": "number"
+              },
+              "type": "object"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "Goals per bin: '0-15','15-30','30-45','45+','46-60','60-75','75-90','90+'"
+        },
+        "first_half_pct": {},
+        "late_share_pct": {
+          "description": "% of goals from 75′ on"
+        },
+        "peak_bins": {
+          "anyOf": [
+            {
+              "items": {
+                "type": "string"
+              },
+              "type": "array"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "Bin(s) with most goals — ties are listed; report a tie as a tie"
+        },
+        "peak_goals": {},
+        "team": {
+          "type": "string"
+        },
+        "total": {}
+      },
+      "required": [
+        "team"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

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

changedOutput schema / properties / stats / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "properties": {
-      "late_goals": {
-        "$ref": "#/properties/stats/anyOf/0/properties/total_goals"
-      },
-      "match_count": {
-        "$ref": "#/properties/stats/anyOf/0/properties/total_goals"
-      },
-      "most_active_period": {
-        "$ref": "#/properties/league"
-      },
-      "total_goals": {}
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "properties": {
+      "late_goals": {},
+      "match_count": {},
+      "most_active_period": {},
+      "total_goals": {}
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / team_filter / $ref
```
Removed value: -"#/properties/league"
```
removedOutput schema / properties / team_not_found / $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."

Changed2 schema fields changedSep 6, 2026

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"
+      ]
+    },
+    "data": {
+      "anyOf": [
+        {
+          "items": {
+            "additionalProperties": true,
+            "properties": {
+              "bins": {
+                "anyOf": [
+                  {
+                    "additionalProperties": {
+                      "type": "number"
+                    },
+                    "type": "object"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ],
+                "description": "Goals per bin: '0-15','15-30','30-45','45+','46-60','60-75','75-90','90+'"
+              },
+              "first_half_pct": {
+                "$ref": "#/properties/data/anyOf/0/items/properties/late_share_pct"
+              },
+              "late_share_pct": {
+                "description": "% of goals from 75′ on"
+              },
+              "peak_bins": {
+                "anyOf": [
+                  {
+                    "items": {
+                      "type": "string"
+                    },
+                    "type": "array"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ],
+                "description": "Bin(s) with most goals — ties are listed; report a tie as a tie"
+              },
+              "peak_goals": {
+                "$ref": "#/properties/stats/anyOf/0/properties/total_goals"
+              },
+              "team": {
+                "type": "string"
+              },
+              "total": {
+                "$ref": "#/properties/stats/anyOf/0/properties/total_goals"
+              }
+            },
+            "required": [
+              "team"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "league": {},
+    "note": {
+      "$ref": "#/properties/league"
+    },
+    "season": {
+      "$ref": "#/properties/league"
+    },
+    "stats": {
+      "anyOf": [
+        {
+          "additionalProperties": true,
+          "properties": {
+            "late_goals": {
+              "$ref": "#/properties/stats/anyOf/0/properties/total_goals"
+            },
+            "match_count": {
+              "$ref": "#/properties/stats/anyOf/0/properties/total_goals"
+            },
+            "most_active_period": {
+              "$ref": "#/properties/league"
+            },
+            "total_goals": {}
+          },
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "team_filter": {
+      "$ref": "#/properties/league"
+    },
+    "team_not_found": {
+      "$ref": "#/properties/league"
+    },
+    "time_bins": {
+      "anyOf": [
+        {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint). The description goes beyond them by disclosing output semantics: the 0-15 to 90+ bucketing, that ties for peak period are listed together, and that the team filter is a substring match on name. It does not address rate limits or tier constraints (those live in the schema), but the added behavioral context is genuine.

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?

Two sentences, front-loaded with the primary output description before the filter clause. It is dense and runs long but every clause contributes information about the returned shape. Minor loss of structure from packing many output facets into a single sentence.

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?

An output schema exists, so return values need not be spelled out, and annotations carry the safety profile. The description covers scope, granularity, tie handling and the filter, which is enough for correct invocation. It omits any pointer to list_leagues for obtaining league/season keys, though the schema supplies that reference.

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 league keys, season formats and the team substring filter in detail. The description restates the team filter behavior ('limits the result to teams whose name contains the given text') but adds no syntax or format detail beyond the schema. Baseline 3 applies.

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 (Returns) and a precisely scoped resource: goals bucketed per 15-minute period, per team, across one league season, including peak periods, late-goal share, first-half share and league totals. This is clearly differentiable from siblings like get_league_table or get_season_projection without opening any schema.

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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative (e.g. versus get_league_table or get_results). Usage is only implicit in the described output, so an agent must infer the scenario rather than being routed to it.

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.