Skip to main content
Glama

AI match summary with lineups

get_match_summary
Read-onlyIdempotent

The Kickwise AI's summary of a team's match: a preview before kickoff, a live reading during the match, or a recap after it, written from the match facts (recent form, confirmed lineups and injuries, formations, statistics and key moments), with both starting lineups and formations once they are announced, the AI's call and the kickwise.ai match page.

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

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 "Liverpool".
opponentNoThe other team, to pick one match.

Output Schema

NameRequiredDescriptionDefault
noteYes
matchYes
queryYes
lineupsYes
summaryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful behavior: the summary is derived from specific match facts and lineups appear only 'once they are announced', warning the agent that content varies with match state and data availability.

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?

It is a single long run-on sentence with a dense parenthetical list of data sources and outputs. The core statement is front-loaded, but the trailing enumeration ('the AI's call and the kickwise.ai match page') is hard to parse and would be clearer as a short structured list.

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 an output schema present and rich annotations, the description needn't explain return values, and it covers content sources and phase-dependent availability well. The remaining gap is behavioral ambiguity when a team has multiple matches, which is only partly resolved by the schema's opponent description.

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 coverage is 100% and the schema itself explains team, opponent (to pick one match) and the lang fallback rules. The description adds no meaning beyond that — it never mentions the opponent parameter or how match disambiguation works, so 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?

Names a specific resource (a team's match AI summary) and enumerates its three modes — preview before kickoff, live reading, recap after — plus the content it draws on. It does not explicitly distinguish itself from the sibling get_match_prediction, even though it mentions 'the AI's call' as part of the payload, leaving overlap ambiguous.

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?

The three temporal modes imply when the tool is useful (pre-match, in-play, post-match), but there is no explicit instruction such as 'use this for narrative summaries, use get_match_prediction for probabilities', and no prerequisites or exclusions are stated.

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