Skip to main content
Glama

footballcharts-mcp

by io.github.ddevetak

League table

get_league_table
Read-onlyIdempotent

Standings for one league season: one row per team with position, played, W/D/L, goals, points, last-five form, plus expected points and a luck category (how far results run ahead of or behind the underlying numbers). Use for "who is top", "how many points", "what is the form", or any question about the table as ranked by points. view="luck" re-orders the same rows by over/under-performance (who is lucky, unlucky, flattered by the table); view="goals" by scoring. For one team in depth use get_team; for how the season is projected to END use get_season_projection. Omit season for the current one. Example: "Is Hull really a top-four side?" → get_league_table premier, view=luck, compare points with expected_points.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
viewNoRow order; default 'classic' (by points)
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
viewNo
tableNo
leagueNo
seasonNo
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. Changed5 schema fields changed
    • addedInput schema / properties / view / anyOf
      Added value: +[
+  {
+    "enum": [
+      "classic",
+      "luck",
+      "goals"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / view / description
      Previous value: -"Ranking view; default 'classic'"New value: +"Row order; default 'classic' (by points)"
    • removedInput schema / properties / view / enum
      Removed value: -[
-  "classic",
-  "luck",
-  "goals"
-]
    • removedInput schema / properties / view / type
      Removed value: -"string"
    • 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"
+      ]
+    },
+    "current_season": {
+      "$ref": "#/properties/league"
+    },
+    "league": {},
+    "season": {
+      "$ref": "#/properties/league"
+    },
+    "season_state": {
+      "$ref": "#/properties/league",
+      "description": "'in_season' or 'finished'"
+    },
+    "table": {
+      "anyOf": [
+        {
+          "items": {
+            "additionalProperties": true,
+            "properties": {
+              "avg_goals_conceded": {
+                "$ref": "#/properties/table/anyOf/0/items/properties/avg_goals_scored"
+              },
+              "avg_goals_scored": {
+                "$ref": "#/properties/table/anyOf/0/items/properties/expected_points"
+              },
+              "clean_sheets": {
+                "$ref": "#/properties/table/anyOf/0/items/properties/position"
+              },
+              "drawn": {
+                "$ref": "#/properties/table/anyOf/0/items/properties/position"
+              },
+              "expected_points": {
+                "description": "Points the underlying numbers say the team should have"
+              },
+              "expected_position": {
+                "$ref": "#/properties/table/anyOf/0/items/properties/position"
+              },
+              "goal_difference": {
+                "$ref": "#/properties/table/anyOf/0/items/properties/position"
+              },
+              "goals_against": {
+                "$ref": "#/properties/table/anyOf/0/items/properties/position"
+              },
+              "goals_for": {
+                "$ref": "#/properties/table/anyOf/0/items/properties/position"
+              },
+              "last_5_form": {
+                "$ref": "#/properties/league",
+                "description": "Latest results as letters, e.g. 'WWDLW'"
+              },
+              "last_5_points": {
+                "$ref": "#/properties/table/anyOf/0/items/properties/position"
+              },
+              "lost": {
+                "$ref": "#/properties/table/anyOf/0/items/properties/position"
+              },
+              "luck_category": {
+                "$ref": "#/properties/league",
+                "description": "'lucky' | 'fair' | 'unlucky'"
+              },
+              "luck_difference": {
+                "$ref": "#/properties/table/anyOf/0/items/properties/expected_points",
+                "description": "points − expected_points; positive = ahead of the numbers"
+              },
+              "over_25_percentage": {
+                "$ref": "#/properties/table/anyOf/0/items/properties/avg_goals_scored"
+              },
+              "played": {
+                "$ref": "#/properties/table/anyOf/0/items/properties/position"
+              },
+              "points": {
+                "$ref": "#/properties/table/anyOf/0/items/properties/position"
+              },
+              "position": {},
+              "team": {
+                "type": "string"
+              },
+              "won": {
+                "$ref": "#/properties/table/anyOf/0/items/properties/position"
+              }
+            },
+            "required": [
+              "team"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "view": {
+      "$ref": "#/properties/league"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare the tool read-only, idempotent, and non-destructive, so the description doesn't need to repeat that. It adds genuinely useful behavioral detail beyond the annotations: rows are one per team, view='luck' re-orders the same rows by over/under-performance rather than filtering, and the free tier only serves current and previous seasons. No contradictions with annotations.

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 dense but each sentence carries weight: definition, use cases, view behavior, sibling routing, season hint, and example. It only loses a point for slight redundancy, such as restating 'Omit for the current season' which is already in the season parameter's schema description. Still, it is well-structured and front-loaded with the core purpose.

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?

An output schema exists, so the description doesn't need to explain return values. It covers the essential operational context: row semantics, column contents, view variants, season behavior, and the free-tier limitation. With the annotations covering safety, an agent has everything needed to select this tool and invoke it correctly without ambiguity.

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 already 3. The description adds meaning beyond the schema by explaining what each view does in behavioral terms ('view="luck" re-orders the same rows by over/under-performance... view="goals" by scoring') and by providing a concrete example query. This goes beyond the schema's terse 'Row order; default classic' label, though it doesn't independently document parameter syntax.

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 opens with a clear definition: 'Standings for one league season: one row per team with position, played, W/D/L, goals, points, last-five form, plus expected points and a luck category.' This specifies both the resource (league table) and the content of each row. It also proactively distinguishes itself from siblings by naming get_team for in-depth team data and get_season_projection for projected final standings.

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?

Explicit usage guidance is provided: 'Use for "who is top", "how many points", "what is the form", or any question about the table as ranked by points.' It also names alternatives and when to choose them: 'For one team in depth use get_team; for how the season is projected to END use get_season_projection.' This is exactly the kind of when-to-use vs. when-not-to guidance an agent needs.

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