Skip to main content
Glama

AI prediction for a match

get_match_prediction
Read-onlyIdempotent

Find a team's match (live, in the coming days, or played in the last two weeks) and the Kickwise AI's call for it: home win, draw and away win chances and its pick, made before kickoff, and its exact score prediction from about an hour before kickoff once the lineups are out. For a finished match it says whether the pick and the exact score were right. Displays HTML prediction cards with team crests and percentage bars when the client supports UI.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
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.
teamYesA team in the match, for example "Arsenal" or "Real Madrid".
opponentNoThe other team, to pick one match.

Output Schema

NameRequiredDescriptionDefault
langYes
noteYes
queryYes
matchesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description is free to add genuinely new behavior: the pick is made before kickoff, the exact score arrives only around an hour pre-match once lineups are out, and finished matches report whether pick and score were correct. It also discloses that HTML prediction cards render only when the client supports UI, which is otherwise undiscoverable.

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?

Two sentences, front-loaded with the action and the match window before moving to prediction timing and UI rendering. The first sentence is clause-dense but every clause carries distinct information; minor tightening is possible but nothing is filler.

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 lookup with a full output schema and richly documented parameters, this covers the remaining gaps: which match is selected, when each prediction tier becomes available, and how UI rendering varies by client. It does not say what happens when a team has several qualifying matches and no `opponent` is given, which is the one ambiguity left.

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

Parameters4/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, and the description earns an increment by explaining the temporal window that determines which match is resolved for a given team — context the schema does not carry. It adds little about `lang` or `opponent` beyond what the schema already documents at length.

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?

The description uses a specific verb and resource ("Find a team's match") and enumerates exactly what the prediction payload contains: home/draw/away chances, the pick, and an exact-score prediction. It also scopes the match window (live, coming days, last two weeks), which makes the tool's remit unambiguous. It stops short of naming how it differs from siblings like get_predictions or get_match_summary.

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

Usage Guidelines3/5

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

Usage is implied through the match window and the note that `opponent` exists "to pick one match," so an agent can infer this is the per-team prediction lookup. There is no explicit when-to-use/when-not-to-use statement and no routing to the sibling tools that also surface predictions.

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