Skip to main content
Glama

Footalytics

get_match_prediction

AI football prediction: combines the algorithm with live data, analyses the match in depth, and predicts the score. Returns win/draw/loss probabilities, confidence, Over/Under 2.5 and Both-Teams-To-Score. Keep those numbers in the answer. Team names must be English (Arsenal, not 阿森纳). Uses 1 credit per successful call. Identify the match with fixture= OR home+away (date optional, UTC).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_match_prediction"
  }
}

Input Schema

NameRequiredDescriptionDefault
awayNoAway team name in English, e.g. Chelsea. Chinese names do not resolve.
dateNoOptional kick-off date YYYY-MM-DD (UTC), disambiguates rematches
homeNoHome team name in English, e.g. Arsenal. Chinese names do not resolve.
fixtureNoFixture id, e.g. 592345 or ESPN-592345

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and does disclose the costly traits: 1 credit per successful call (implying failures are not charged) and a hard input constraint that Chinese team names do not resolve. It does not cover edge behavior such as unmatched or ambiguous matches, which an agent would need before retrying.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is dense and front-loaded — capability, then return values, then cost, then identification rules. The one sentence that is really an instruction to the answering agent ("Keep those numbers in the answer") is arguably out of scope for a tool description, but the rest of the text is efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations, the description compensates well by naming the return fields and the credit cost, so an agent knows what comes back and what it pays. The only gap is failure handling (ambiguous fixture, unresolved team name), which matters given that identification is optional-by-either-path.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds something the schema cannot express: that fixture OR home+away are alternative identification strategies. Since the schema lists all four parameters as optional with no required set, this OR relationship is genuinely new meaning that prevents an agent from calling with zero or conflicting identifiers.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

"AI football prediction" followed by an explicit statement of what it produces (win/draw/loss probabilities, confidence, Over/Under 2.5, Both-Teams-To-Score) gives a concrete verb+resource plus the output shape. Nothing in the sibling list (credits, team, fixtures, results) overlaps with this predictive operation, so an agent can select it without ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description states the two valid identification modes (fixture=<id> OR home+away, with date optional) and the language constraint for team names, which is real when-to-use guidance for invocation. It stops short of naming alternatives — e.g. pointing at list_fixtures to obtain a fixture id before calling — and gives no when-not-to-use condition.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources