Skip to main content
Glama
Sign In

footballcharts-mcp

by io.github.ddevetak
OverviewDiscussionsAdmin

List leagues

list_leagues
Read-onlyIdempotent

Returns every league covered (98 across 44 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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_leagues"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output 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, so the safety profile is covered; the description adds the non-obvious bits: exhaustive coverage (98 leagues), newest-first ordering, and that it takes no parameters. It does not discuss pagination or result size limits, which for a 98-item response would be the remaining useful detail.

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: content, then the cross-tool contract, then the format rule. The most decision-relevant facts (what you get, why you need it) are front-loaded with 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?

With an output schema present, return values need not be spelled out, yet the description still previews the four fields an agent will use. For a zero-parameter, read-only discovery tool this covers everything needed to call it correctly and interpret the result.

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?

Zero parameters gives the baseline of 4, and the description correctly confirms "No parameters" so an agent will not hunt for filters. It also documents the season-string format variants ('2026-2027' vs '2026'), which is meaningful semantics even though those strings are outputs consumed by siblings rather than inputs here.

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 then enumerates exactly what each entry carries: league key, display name, country, available seasons. The scope (98 leagues, 44 countries) and ordering (newest first) make it unambiguous against siblings like get_league_table or get_fixtures.

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?

"Other tools take these league keys and season strings" positions this as the discovery entry point that must be called before the key-consuming siblings, which is the critical routing signal. It stops short of naming a specific alternative or an explicit when-not condition, so it is not a full 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