Skip to main content
Glama

footballcharts-mcp

by io.github.ddevetak
OverviewDiscussionsAdmin

List leagues

list_leagues
Read-onlyIdempotent

Returns every league covered (93 across 42 countries) with its league key, display name, country and the seasons available, newest first. Other tools take these league keys and season strings. Season format depends on the competition: '2026-2027' for winter-calendar leagues, '2026' for summer-calendar leagues. No parameters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNo
leaguesYes
attributionNoCite as "Data by football-charts.com"
season_windowNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedOutput schema / properties / season_window / $ref
      Removed value: -"#/properties/leagues/items/properties/url"
  2. 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"
+      ]
+    },
+    "count": {},
+    "leagues": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "country": {
+            "type": "string"
+          },
+          "league": {
+            "description": "The key to pass as `league`",
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "seasons": {
+            "description": "Newest first; exact strings for `season`",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "url": {}
+        },
+        "required": [
+          "league",
+          "name",
+          "country",
+          "seasons"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "season_window": {
+      "$ref": "#/properties/leagues/items/properties/url"
+    }
+  },
+  "required": [
+    "leagues"
+  ],
+  "type": "object"
+}
  3. 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 readOnly, idempotent, non-destructive, and open-world behavior, so the safety and side-effect profile is covered. The description adds real behavioral context beyond that: the result set is exhaustive (93 leagues / 42 countries), ordered newest-first, and takes no parameters. It stops short of describing pagination or output shape, but that is minor given the output schema.

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 tight sentences, front-loaded with what is returned and how many, followed by the downstream-key relationship and the season-format detail. Every sentence carries distinct information with no redundancy.

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 no-parameter enumeration tool with an output schema already defining the return shape, the description covers scope, ordering, and the cross-tool contract for keys and season strings. An agent has everything needed to call it and to use its output correctly.

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?

With zero parameters, the baseline is 4. The description goes further by documenting the season string format used by consuming tools ('2026-2027' for winter-calendar, '2026' for summer-calendar), which adds meaning an agent would otherwise have to guess.

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 ('Returns every league covered') and enumerates exactly what each entry contains: league key, display name, country, and available seasons. This is clearly distinguishable from siblings like get_league_table or get_fixtures, which operate on a single league rather than enumerating all of 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?

The description situates the tool in a workflow: 'Other tools take these league keys and season strings,' making it clear this is a discovery/lookup call that feeds downstream tools. It does not state explicit exclusions or when-not-to-use conditions, so it falls short of a 5.

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
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.

Resources