SportScore
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 |
|---|---|
| get_matchesA | List live and recent matches for a sport. Returns up to |
| get_match_detailA | Get detailed data for a single match by its slug (e.g. 'manchester-united-vs-liverpool'): score, status, timeline, lineups. Slugs come from get_matches results or match URLs on sportscore.com. |
| get_team_scheduleA | Get a team's past and upcoming fixtures by team slug (e.g. 'barcelona', 'manchester-united', 'los-angeles-lakers'). |
| get_standingsA | Get the current standings table for a league or competition by slug (e.g. 'premier-league', 'la-liga', 'nba'). |
| get_top_scorersA | Get the top scorers (or top assisters) for a competition. Useful for 'who's leading the Premier League scoring charts?'. |
| get_playerA | Get player statistics and metadata by player slug (e.g. 'lionel-messi', 'lebron-james', 'virat-kohli'). |
| get_bracketA | Get the knockout bracket for a tournament (e.g. 'uefa-champions-league', 'nba-playoffs'). |
| get_trackerA | Get live match tracker data (position, animation frames) for a match by numeric id. Usually only useful for football. |
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 8 tools
Each tool targets a distinct aspect of sports data (brackets, match detail, list matches, players, standings, schedule, top scorers, live tracker) with no overlapping purposes. The descriptions clearly differentiate them.
All tool names follow a consistent `get_` prefix followed by a descriptive noun in snake_case (e.g., get_bracket, get_match_detail). The pattern is uniform and predictable.
With 8 tools, the server covers a broad range of common sports queries without being excessive or insufficient. Each tool has a clear role, making the set well-scoped for its domain.
The tools cover core sports data needs: matches, details, standings, schedules, players, top scorers, brackets, and live tracking. A minor gap is the lack of team or league metadata tools, but the surface is largely complete for typical use cases.