Skip to main content
Glama

Football predictions by day or league

get_predictions
Read-onlyIdempotent

The Kickwise AI's predictions for football matches today or tomorrow, or for one league over the coming days: for each match the chance of a home win, a draw and an away win, the AI's pick, its exact score prediction (made about an hour before kickoff, once the lineups are out), the kickoff time (UTC), the live or final score when there is one, and the kickwise.ai match page. Displays HTML prediction cards with team crests and percentage bars when the client supports UI.

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_predictions"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayNotoday (default) or tomorrow.
langNoLanguage for card labels, team names, AI summaries and linked kickwise.ai pages. Pass the user's requested language when it is en, es, fr, ar or pt; for any other language pass en and translate the relevant text in your answer. An explicit lang overrides the client locale. When omitted, a supported client locale is used, else en.
leagueNoLimit to one league. Without a day, lists its matches over the coming days.

Output Schema

NameRequiredDescriptionDefault
dayYes
langYes
noteYes
totalYes
leagueYes
matchesYes
page_urlYes
record_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world behavior, so the description needn't restate them. It adds genuinely new operational context: the exact-score prediction is generated about an hour before kickoff once lineups are out (so it may be absent earlier), kickoff times are UTC, and HTML cards render only when the client supports UI.

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

Conciseness3/5

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

The lead clause front-loads the purpose well, but the long mid-sentence enumeration of return fields (win/draw/away probabilities, pick, exact score, kickoff, live score, match page) largely duplicates the available output schema and bloats the definition. The timing caveat and UI-rendering note are the parts that genuinely earn their place.

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?

For a read-only, three-optional-parameter tool with a full output schema, the definition is essentially complete: scope, language handling context, prediction timing, and UI fallback are all covered. Minor gaps like empty-result behavior when no matches exist are acceptable given the schema and annotations.

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

Parameters3/5

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

Schema description coverage is 100% and all three parameters are fully documented in-schema, including the lang fallback rules and the day-less league behavior. The description only restates the day/league semantics, adding no format or edge-case detail beyond the schema, so the baseline 3 applies.

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

Purpose4/5

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

States a specific verb+resource (AI predictions for football matches) with exact scope: today, tomorrow, or one league over the coming days. The scope wording implicitly differentiates it from the single-match sibling get_match_prediction, but no sibling is ever named, so it falls short of full 5-level differentiation.

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 makes the selection conditions concrete: use it for today/tomorrow, or for one league across the coming days. It gives no explicit exclusion or 'use X instead' routing, so the agent must infer that get_match_prediction covers a single fixture.

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