iddaa-mcp
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_competitionsB | Fetch competitions from Iddaa sportsbook API |
| get_eventsC | Fetch sports events from Iddaa sportsbook API |
| get_detailed_eventsC | Fetch events with matched organization names and competition details |
| get_highlighted_eventsC | Fetch highlighted events |
| get_league_fixtureC | Fetch fixture data for selected leagues from archive source |
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 5 tools
get_events, get_detailed_events, and get_highlighted_events all fetch event data, with the latter two being specialized variants. While descriptions differentiate them, the generic get_events overlaps conceptually with get_detailed_events, requiring careful reading to choose correctly.
All tools follow a consistent get_<resource> pattern with snake_case, making the API predictable and easy to navigate.
Five tools is an appropriate size for a focused sportsbook API client, covering core data types without unnecessary bloat.
The tool set provides competition and event data, but lacks odds or market information, which is a core component of a sportsbook. This creates a notable gap for users expecting betting-related functionality.