Skip to main content
Glama

footballcharts-mcp

by io.github.ddevetak

Match results

get_results
Read-onlyIdempotent

Finished matches of one league season, one row per match: date, teams, full-time and half-time score, first-goal minute, goalless flag. Rows are in chronological order, earliest first. last=N keeps only the N latest matches and still returns them earliest-first. team filters on a case-insensitive substring of either side's name. Use for scores, "how did X do lately", head-to-head within a season, half-time scores or first-goal minutes. Use get_fixtures for matches not yet played, get_match for one match's probability detail, get_team for one team's season in full. No odds. Example: "Last five Liverpool results" → get_results premier, team="Liverpool", last=5.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lastNoKeep only the N latest matches of the season, e.g. 5 for recent form (default: all)
teamNoTeam name substring, e.g. 'Liverpool'
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
noteNo
countNo
leagueNo
seasonNo
matchesNo
attributionNoCite as "Data by football-charts.com"
season_stateNo'in_season' or 'finished'
current_seasonNo

Schema Changelog

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

  1. Changed7 schema fields changed
    • 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"
+}
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

The description clearly discloses behavioral details beyond the annotations: rows are chronological, last=N returns the N latest still ordered earliest-first, team filters case-insensitively on either side's name, and odds are not included. The readOnly/idempotent annotations already cover safety, and this description adds meaningful operation semantics without contradicting them.

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: purpose, output rows, ordering, filter semantics, usage scenarios, sibling alternatives, limitation, and a worked example. Information is front-loaded with the core purpose before details, and nothing feels redundant or 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?

Given that an output schema exists, annotations cover safety, and the schema documents all parameters, the description is complete for an agent to select and invoke the tool correctly. It covers selection criteria, parameter behavior, exclusions, and gives a realistic example, leaving no important operational gap.

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?

The schema already covers all parameters at 100%, so the baseline is 3. The description adds value beyond the schema by explaining that last preserves chronological order, team matches a case-insensitive substring of either side, and providing example league keys and season format nuances. This is more than repetition, though not all of it is required given the rich schema.

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 identifies a specific resource ('Finished matches of one league season') and output granularity (one row per match with listed fields). It also explicitly distinguishes itself from siblings by naming get_fixtures, get_match, and get_team, so an agent can tell exactly what this tool returns.

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 provides explicit when-to-use guidance: scores, recent form, head-to-head, half-time scores, and first-goal minutes. It also names alternatives with their conditions: get_fixtures for unplayed matches, get_match for probability detail, and get_team for full season team view, plus a concrete example mapping the query 'Last five Liverpool results' to parameters.

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