Skip to main content
Glama

SportStatsAPI

Get team briefing

get_team_briefing
Read-only

Ready briefing for one team (any sport but cricket; for tennis a player): form, streaks (overall, home, away; streak_season_best: the longest of the season), home and away record, table place and gaps, last and next match, congestion (games_last_7d, games_last_14d in every competition, rest_days from the last match to the next), injuries (soccer); what its last match ended (runs; soccer: first_since_* waits); soccer player milestones for the club (debut, first goal, 50/100/150 league appearances, 25/50/75 league goals, milestone_next before the next match; only when our statistics hold the whole season); each also as a sentence (lang de, es, it, fr), and summary: the most important ones as one paragraph. Facts only. Part of the Insights feature.

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_id": "<team_id>"
    },
    "name": "get_team_briefing"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNolanguage of team, league and country names: de, es, it or fr (default English)
sportNosport (default soccer); for tennis the id is a player id
formatNomd for a short Markdown text instead of JSON
team_idYesteam code (or number) from find_teams or a match (tennis: player id)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / team_id / description
      Previous value: -"team id from find_teams or a match (tennis: player id)"New value: +"team code (or number) from find_teams or a match (tennis: player id)"
  2. Changed1 schema field changed
    • changedInput schema / properties / team_id / type
      Previous value: -"integer"New value: +[
      +  "integer",
      +  "string"
      +]
  3. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover read-only safety, so the description's added value is in disclosing conditional behavior: injuries only for soccer, soccer milestones only when statistics hold the whole season, and milestone_next reported before the next match. "Facts only" and the md-vs-JSON option further set expectations. What it lacks is any mention of failure behavior for an invalid team_id or of result size.

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 front-loaded with the core purpose, but the body is a single long semicolon-chained sentence mixing field names, conditionals, and localization notes. Every clause carries information, yet the dense parenthetical style makes it harder to scan than a short bulleted structure would.

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, the description carries the burden of describing the return payload and does so thoroughly, including the sentence-per-fact localization and the one-paragraph summary. It does not cover error cases or how large the briefing can get, but for a read-only composite report it is largely complete.

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%, so all four parameters are already documented there, including the lang values and the tennis player-id meaning of team_id. The description mostly restates those points (cricket exclusion, tennis id) without adding syntax, defaults, or edge-case guidance beyond the schema.

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 opens with a specific verb and resource ("Ready briefing for one team") and then enumerates the concrete payload (form, streaks, table gaps, congestion, injuries, milestones, summary), which clearly separates it from a plain team-lookup tool like get_team. It does not explicitly name any sibling, so the differentiation is implicit rather than stated.

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 only implied through scope constraints: "any sport but cricket", tennis takes a player instead of a team, and it is framed as "Part of the Insights feature." There is no statement of when to prefer this over get_team, get_match_briefing, or get_summary, and no prerequisites are given.

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