FotMoCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_fotmobB | Search names and get FotMob IDs for teams, players, leagues, and matches. |
| find_matchesA | List FotMob matches on a UTC date. Use it when you do not have a match ID. |
| get_team_season_profileC | Get a team's table record, xG, xGA, xPoints, and FIFA ranking when present. |
| get_team_availabilityC | List injured players and their reported return dates. |
| get_player_workloadC | Get a player's recent minutes, last appearance, and injury status. |
| get_goalkeeper_match_statsA | Get saves, shots on target faced, save percentage, xGOT faced, and goals prevented. matchId may be an ID or FotMob URL. |
| get_team_game_state_recordC | Count recent wins, draws, and losses after a team led or trailed. |
| get_match_prediction_contextB | Get the clock, events, lineups, momentum, form, head-to-head, weather, venue, and competition. matchId may be an ID or FotMob URL. |
| get_team_formC | Get recent results and home/away splits, with ranking and per-match xG when present. |
| get_match_statsC | Get the score plus deduplicated team and player stats. matchId may be an ID or FotMob URL. |
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 10 tools
Each tool targets a distinct purpose: match discovery, specific stat categories, prediction context, team/player details, etc. No two tools appear interchangeable.
All tools follow a clear verb_noun snake_case pattern (e.g., find_matches, get_goalkeeper_match_stats), providing predictable naming.
10 tools cover the core football data domains (matches, teams, players, stats) without being overwhelming or too sparse.
The tool set covers search, match details, team/player stats, injury updates, and prediction context. A minor gap is the lack of a direct league standings tool, but overall coverage is solid.