Tulospalvelu MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PALLOLIITTO_BASE_URL | No | Base URL for the Palloliitto API. | https://spl.torneopal.net/taso/rest |
| PALLOLIITTO_ACCEPT_HEADER | Yes | Accept header value required for API requests. | |
| PALLOLIITTO_REQUEST_TIMEOUT_MS | No | Request timeout in milliseconds. | 10000 |
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 |
|---|---|
| search_entitiesC | Search Palloliitto entities such as competitions, categories, clubs, teams, players, venues, and matches. |
| list_seasonsC | List seasons for a sport. Football is the default. |
| list_competitionsC | List competitions by season and organiser filters. |
| get_competitionB | Get a single competition by its Palloliitto competition ID. |
| list_categoriesC | List categories for a competition. |
| get_league_tableB | Get detailed league table data, standings, player statistics, and optionally matches for a single group. |
| list_matchesC | List matches by date and filters, or run Taso text search mode. |
| get_matchC | Get detailed match data for a single match ID. |
| get_match_scoreC | Get the current or final score for a single match ID. |
| list_teamsC | List teams in a competition, optionally filtered by category. |
| get_teamA | Get current roster data for a team, or historical roster data when competitionId and categoryId are both provided. |
| get_playerB | Get player details by Palloliitto player ID. |
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 12 tools
Each tool has a clearly distinct purpose. For example, get_match returns detailed match data while get_match_score returns only the score, and list_competitions vs get_competition differentiate between listing and single retrieval. No two tools overlap in functionality.
All tool names follow a consistent verb_noun snake_case pattern (e.g., get_competition, list_matches, search_entities). There are no deviations or mixed conventions, making it predictable for agents.
With 12 tools, the set is well-scoped for a sports data service covering competitions, teams, matches, players, and standings. It provides sufficient granularity without being excessive or too sparse.
The tool surface covers the core domain of a football data API comprehensively: listing and retrieving competitions, seasons, categories, teams, matches, scores, league tables, players, and a general search. While it is read-only, it handles all typical query operations with no obvious gaps.