Skip to main content
Glama
aiballfooty

AI Ball MCP server

by aiballfooty

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
AIBALL_API_BASENoSet AIBALL_API_BASE to point the server at another base URL.

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_matchesA

Matches for one calendar day: match_id, kick-off time (UTC), league, teams and status. status is upcoming (pre-kick-off read is locked), pending (current read, may still change before kick-off) or finished. Pass a match_id to get_match_analysis for the outcome probabilities and, once played, the result.

get_match_analysisA

For one match: the model's home / draw / away probabilities as recorded before kick-off (fractions that sum to 1), its most likely outcome, a confidence score, the pre-match favourite, and when the read was captured. For a finished match it also returns the final score and whether the most likely outcome happened (hit). This version returns the balanced model; models_available lists what is included.

get_open_recordA

How the model's pre-kick-off reads turned out. Without arguments: the whole public record. With week_start: one Monday-to-Sunday week. Returns matches counted (n), how many went the model's way (hits), the same matches scored by always taking the pre-match favourite and by one in three, and the breakdown by confidence band. hit_rate is a percentage; null means the sample is under min_band_sample, so quote the counts instead. Misses are counted the same way as hits.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 3 tools

Disambiguation5/5

The three tools target clearly distinct scopes: list_matches discovers matches for a day, get_match_analysis drills into one match's probabilities, and get_open_record reports aggregate performance. There is no functional overlap between them.

Naming Consistency4/5

All three follow a verb_noun pattern (list_matches, get_match_analysis, get_open_record), which is predictable and readable. The slightly odd term 'open_record' is a minor deviation but the convention itself is consistent.

Tool Count4/5

Three tools is lean but each maps to a distinct need (discovery, per-match detail, aggregate record). It is slightly thin for a data service but nothing feels redundant or missing at the top level.

Completeness3/5

Core flow — find matches, analyze a match, check the record — is covered, but notable gaps remain: no multi-day or date-range query, no league/team filtering, and no way to look up a specific match directly without a daily listing. These force workarounds for common agent requests.

Maintenance

ActivityMaintained
ResponsivenessNo issues