profixio
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_federationsA | List the sports federations on Profixio (e.g. SHF = Svenska Handbollförbundet, SVBF = volleyboll). Start here to browse. |
| list_districtsA | List the districts/regions of a federation, e.g. SHF → HF Öst, HF Väst. |
| list_competitionsA | List the competitions (series/leagues) for the current season, either federation-wide (national series) or in one district. Returns slugs used by the other tools. |
| search_teamsA | Search all of Profixio for teams by name. Returns team ids with the competition each team plays in (newest seasons first is not guaranteed). |
| get_competition_matchesA | Schedule and results for a competition. Each match has a matchId to pass to get_match_protocol. |
| get_team_matchesB | All matches for one team in a competition. Use search_teams or get_competition_matches to find the teamId. |
| get_standingsB | League table(s) for a competition. One competition can have several groups. |
| get_matches_by_dateC | All matches in a district on a given day. |
| get_match_protocolB | The match protocol (matchprotokoll): teams, result, venue, lineups with goals and suspensions per player, officials, and the full event log (goals, 7m, suspensions, timeouts). |
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 9 tools
Most tools are clearly distinct by resource and filter: federation/district/competition browsing, team search, standings, and match protocol are well separated. The three match-retrieval tools (get_competition_matches, get_team_matches, get_matches_by_date) overlap in returning match lists, but their descriptions make the filter differences reasonably clear.
All tool names consistently follow a snake_case verb_noun pattern (list_*, search_*, get_*), with predictable resource names. There are no mixed conventions or vague verbs.
Nine tools is well-scoped for browsing federations, districts, competitions, teams, schedules, standings, and match protocols. Each tool covers a distinct step in the sports-data workflow without obvious redundancy.
The surface covers the core browse-and-retrieve workflow: hierarchy navigation, team search, schedules/results, standings, and detailed match protocols. Minor gaps exist, such as no explicit season selection or team/player profile tools, but these are not dead ends for the main use cases.