Skip to main content
Glama

SportStatsAPI

Get bracket

get_bracket
Read-only

A knock-out bracket: rounds in playing order, ties with their legs, aggregate (soccer: goals after extra time), the side that advanced and how (score, aggregate, extra_time, penalties, walkover, next_round), and from: the tie a side won to get there. Soccer cups and the European knock-out phases (league_id, season); tennis draws (league_id: the category id, season: a year), rebuilt from who beat whom (qualifying first; seeds, entry types and draw order where a Wikipedia draw is linked); snooker and darts tournaments (tournament_id). Rounds we cannot prove from stored matches have status missing with a reason and no ties; pairings are never guessed (snooker and darts add 'winner of A v B' placeholders only where the draw's tree is proven).

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": {
      "sport": "<sport>"
    },
    "name": "get_bracket"
  }
}

Input Schema

NameRequiredDescriptionDefault
sportYessoccer, tennis, snooker or darts
seasonNosoccer: 2025-26, 2025/2026 or 2025 (default: the latest season with knock-out rounds); tennis: a year (default: the latest edition)
league_idNosoccer: the cup's league code (or number), from find_leagues; tennis: the tournament's category id
tournament_idNosnooker or darts: tournament code (or number) from get_snooker_darts_tournaments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / league_id / description
      Previous value: -"soccer: the cup's league code (or number), from find_leagues"New value: +"soccer: the cup's league code (or number), from find_leagues; tennis: the tournament's category id"
    • changedInput schema / properties / season / description
      Previous value: -"soccer: 2025-26, 2025/2026 or 2025 (default: the latest season with knock-out rounds)"New value: +"soccer: 2025-26, 2025/2026 or 2025 (default: the latest season with knock-out rounds); tennis: a year (default: the latest edition)"
    • changedInput schema / properties / sport / description
      Previous value: -"soccer, snooker or darts"New value: +"soccer, tennis, snooker or darts"
  2. Added

TDQS

A3.9/5.0
Behavior5/5

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

With only readOnlyHint and openWorldHint supplied by annotations, the description carries real weight and delivers: unprovable rounds surface as status 'missing' with a reason and no ties, pairings are never guessed, and 'winner of A v B' placeholders appear only where the draw tree is proven. These data-provenance caveats are exactly the kind of behavior an agent cannot get from structured fields and would otherwise misreport.

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?

Word count is reasonable for the volume of information, but the content is delivered as one dense run-on with no separation between return shape and caveats, and it partly duplicates the schema's per-sport parameter explanations. Front-loading the return structure is a strength, but the parenthetical piling hurts scanability.

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

Completeness5/5

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

No output schema exists, so the description must define the return shape itself, and it does so explicitly: rounds, ties, legs, aggregate, advancement method enum, and the 'from' back-reference. Combined with the honesty rules about missing rounds and placeholder pairings, an agent has everything needed to call it and interpret the result.

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, including per-sport season formats and which id field applies to which sport, are already documented in the schema. The description restates most of that (tennis league_id as category id, year for season) rather than adding syntax or constraints beyond it, so the baseline of 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?

The opening noun phrase 'A knock-out bracket: rounds in playing order, ties with their legs, aggregate...' tells an agent precisely what resource this returns and in what structure, and the sport/competition coverage lines distinguish it from flat match or standings tools. It stops short of naming a sibling it supersedes, so an agent must infer the boundary with get_matches or get_standings.

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 by competition type: soccer cups and European knock-out phases, tennis draws, snooker and darts tournaments, each mapped to its own id parameter, which is genuinely useful routing information. There is no explicit when-to-use/when-not statement and no named alternative for flat round-by-round fixtures, so the guidance is inferential rather than directive.

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