Skip to main content
Glama

footballcharts-mcp

by io.github.ddevetak

Team page

get_team
Read-onlyIdempotent

Everything held on one team in one league season: its table row (with luck and expected points), the full match log (date, opponent, venue H/A, score, half-time score, first-goal minute, outcome), goals per 15-minute bin, first-goal distribution, and the seasons available. team is a slug: lower-case, spaces as hyphens, e.g. 'arsenal', 'manchester-city'. Take the exact name from get_league_table first when unsure. Use for one team in depth ("tell me about Arsenal's season"). Use get_league_table for every team shallowly, get_results with a team filter for just the scores, get_goal_timing to compare timing across the whole league. Example: "How is Arsenal doing?" → get_team premier, team="arsenal".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
teamYesTeam slug, e.g. 'arsenal', 'manchester-city' (from the table's team names, lower-case, spaces as hyphens)
leagueYesLeague key from list_leagues, e.g. 'premier' (England), 'spain1', 'brazil1', 'sweden1', 'wgermany1' (women). Not the display name.
seasonNoSeason 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.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugNo
teamNo
leagueNo
seasonNo
matchesNo
rankingNoThe team's table row
seasonsNo
attributionNoCite as "Data by football-charts.com"
first_goal_binsNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • 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"
+      ]
+    },
+    "first_goal_bins": {
+      "anyOf": [
+        {
+          "items": {
+            "additionalProperties": true,
+            "properties": {
+              "count": {
+                "$ref": "#/properties/ranking/anyOf/0/properties/position"
+              },
+              "time": {
+                "$ref": "#/properties/team"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "league": {
+      "$ref": "#/properties/team"
+    },
+    "matches": {
+      "anyOf": [
+        {
+          "items": {
+            "additionalProperties": true,
+            "properties": {
+              "away": {
+                "$ref": "#/properties/team"
+              },
+              "date": {
+                "$ref": "#/properties/team"
+              },
+              "first_goal_time": {
+                "$ref": "#/properties/team"
+              },
+              "home": {
+                "$ref": "#/properties/team"
+              },
+              "ht": {
+                "$ref": "#/properties/team"
+              },
+              "outcome": {
+                "$ref": "#/properties/team",
+                "description": "'W' | 'D' | 'L'"
+              },
+              "score": {
+                "$ref": "#/properties/team"
+              },
+              "time": {
+                "$ref": "#/properties/team"
+              },
+              "venue": {
+                "$ref": "#/properties/team",
+                "description": "'H' or 'A'"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "ranking": {
+      "anyOf": [
+        {
+          "additionalProperties": true,
+          "properties": {
+            "avg_goals_conceded": {
+              "$ref": "#/properties/ranking/anyOf/0/properties/avg_goals_scored"
+            },
+            "avg_goals_scored": {
+              "$ref": "#/properties/ranking/anyOf/0/properties/expected_points"
+            },
+            "clean_sheets": {
+              "$ref": "#/properties/ranking/anyOf/0/properties/position"
+            },
+            "drawn": {
+              "$ref": "#/properties/ranking/anyOf/0/properties/position"
+            },
+            "expected_points": {
+              "description": "Points the underlying numbers say the team should have"
+            },
+            "expected_position": {
+              "$ref": "#/properties/ranking/anyOf/0/properties/position"
+            },
+            "goal_difference": {
+              "$ref": "#/properties/ranking/anyOf/0/properties/position"
+            },
+            "goals_against": {
+              "$ref": "#/properties/ranking/anyOf/0/properties/position"
+            },
+            "goals_for": {
+              "$ref": "#/properties/ranking/anyOf/0/properties/position"
+            },
+            "last_5_form": {
+              "$ref": "#/properties/team",
+              "description": "Latest results as letters, e.g. 'WWDLW'"
+            },
+            "last_5_points": {
+              "$ref": "#/properties/ranking/anyOf/0/properties/position"
+            },
+            "lost": {
+              "$ref": "#/properties/ranking/anyOf/0/properties/position"
+            },
+            "luck_category": {
+              "$ref": "#/properties/team",
+              "description": "'lucky' | 'fair' | 'unlucky'"
+            },
+            "luck_difference": {
+              "$ref": "#/properties/ranking/anyOf/0/properties/expected_points",
+              "description": "points − expected_points; positive = ahead of the numbers"
+            },
+            "over_25_percentage": {
+              "$ref": "#/properties/ranking/anyOf/0/properties/avg_goals_scored"
+            },
+            "played": {
+              "$ref": "#/properties/ranking/anyOf/0/properties/position"
+            },
+            "points": {
+              "$ref": "#/properties/ranking/anyOf/0/properties/position"
+            },
+            "position": {},
+            "team": {
+              "type": "string"
+            },
+            "won": {
+              "$ref": "#/properties/ranking/anyOf/0/properties/position"
+            }
+          },
+          "required": [
+            "team"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "The team's table row"
+    },
+    "season": {
+      "$ref": "#/properties/team"
+    },
+    "seasons": {
+      "anyOf": [
+        {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "slug": {
+      "$ref": "#/properties/team"
+    },
+    "team": {}
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds useful behavioral context by defining the team slug rules, instructing the agent to source exact names from get_league_table when unsure, and noting that 'seasons available' are part of the response.

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?

The description is dense but every sentence earns its place: output scope, slug guidance, usage routing, and an example. It is front-loaded with the most important information and contains no filler.

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 3-parameter read-only tool with a full output schema and rich annotations, the description covers what is returned, how to form parameters, when to use it versus alternatives, and gives a worked example. Nothing an agent needs 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.

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, team, and season. The description reinforces team slug format and gives a full example call, but it does not add substantial semantic information beyond what the parameter descriptions already provide.

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 names the exact resource (one team in one league season) and enumerates the payload: table row, match log, goal bins, first-goal distribution, and seasons. It clearly separates this from sibling tools by framing it as the in-depth single-team endpoint.

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

Usage Guidelines5/5

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

The description gives explicit when-to-use guidance: 'Use for one team in depth' and contrasts with get_league_table for every team shallowly, get_results for just scores, and get_goal_timing for league-wide timing. It also provides a concrete natural-language-to-call example, making routing unambiguous.

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

All footballcharts-mcp toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.7/5.0
Disambiguation5/5

Each tool targets a clearly distinct resource or query type: fixtures, results, match details, standings, team profiles, goal timing, projections, track record, and league enumeration. Descriptions include explicit cross-references to related tools, eliminating boundary confusion.

Naming Consistency4/5

The dominant pattern is get_ + noun, which is consistent and predictable. list_leagues and about_football_charts are deliberate exceptions that fit their meta/enumeration purposes, but they do break the otherwise uniform convention.

Tool Count5/5

Ten tools is well-scoped for a football data and model-probability server. Each tool covers a meaningful slice of the domain without redundancy or bloat.

Completeness5/5

The tool surface covers the full read-only workflow: discovering leagues, viewing tables, fixtures, results, single matches, team deep-dives, goal timing, season projections, and model credibility. No obvious dead ends or missing operations for the stated purpose.

Resources