mcp-football
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FOOTBALL_DATA_TOKEN | Yes | Your football-data.org API token. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| todays_matchesA | |
| competition_top_scorersA | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one retrieves top scorers for a competition, the other fetches today's matches. There is no overlap or ambiguity.
Both tool names use a descriptive, snake_case format similar to 'noun_verb' or 'adjective_noun'. The apostrophe in 'todays_matches' is a minor inconsistency, but overall naming is consistent.
Only two tools for a football data server is too few. Typical football APIs cover many more endpoints such as team info, standings, player stats, match details, etc. The tool count is insufficient for the domain's scope.
The server provides only two operations: top scorers and today's matches. Lacks essential features like team lookup, league tables, player season stats, match details by ID, and historical data. Significant gaps in coverage.