Season and Historic Bundle Tools

​

Start Here If

• you want a season snapshot in one call
• you need leaderboard or classification-driven views
• you are building team or person season hubs
• you need historical season selection or year-over-year comparison

​

Tool Selection Guide

​

gns_league_season_snapshot

• What it helps you do: build a broad season page in one call.
• When to use it: league hubs, kickoff pages, and “tell me the state of the season” prompts.
• Inputs you need: leagueId or leagueSeasonId, plus optional include flags and language.
• What you get back: season info with optional structure, standings, teams, and classifications.
• Example user questions it can answer: “Give me the whole season picture for this league.”
• Example request:

{
  "name": "gns_league_season_snapshot",
  "arguments": {
    "leagueId": "LEAGUE_ID",
    "includeStructure": true,
    "includeStandings": true,
    "includeTeams": true,
    "includeClassifications": true,
    "language": "en-US"
  }
}

• Expected response summary: one season envelope that covers the core building blocks of a league hub.
• What to call next: gns_team_season_profile, gns_person_season_profile, or gns_historic_season_bundle.

​

gns_league_leaderboards

• What it helps you do: generate normalized top lists from league classifications.
• When to use it: top scorers, assists leaders, and stat-rank experiences.
• Inputs you need: leagueId or leagueSeasonId, optional classificationIds, optional topN, optional language.
• What you get back: selected classification definitions plus ranked results.
• Example user questions it can answer: “Who are the top scorers in this season?”
• Example request:

{
  "name": "gns_league_leaderboards",
  "arguments": {
    "leagueId": "LEAGUE_ID",
    "topN": 10,
    "language": "en-US"
  }
}

• Expected response summary: leaderboard sections ready for a stats tab, season hub, or AI-generated comparison.
• What to call next: gns_classification_info, gns_person_season_profile, or your rendering layer.

​

gns_team_season_profile

• What it helps you do: build a canonical team season hub.
• When to use it: team pages, personalization, or team-summary assistant prompts.
• Inputs you need: teamId, leagueId or leagueSeasonId, optional includeRoster, optional language.
• What you get back: team info, season stats, and optional roster.
• Example user questions it can answer: “Build a season profile for this team.”
• Example request:

{
  "name": "gns_team_season_profile",
  "arguments": {
    "teamId": "TEAM_ID",
    "leagueId": "LEAGUE_ID",
    "includeRoster": true,
    "language": "en-US"
  }
}

• Expected response summary: a reusable team-season envelope with profile, stats, and roster context.
• What to call next: gns_team_schedule_results or gns_live_team_dashboard.

​

gns_person_season_profile

• What it helps you do: build a player or person season hub in one call.
• When to use it: player pages, follow flows, and “how is this person performing?” prompts.
• Inputs you need: personId, leagueId or leagueSeasonId, optional language.
• What you get back: person info and season stats.
• Example user questions it can answer: “Show me this player’s season profile.”
• Example request:

{
  "name": "gns_person_season_profile",
  "arguments": {
    "personId": "PERSON_ID",
    "leagueId": "LEAGUE_ID",
    "language": "en-US"
  }
}

• Expected response summary: a person-season package that is easier to summarize than stitching individual person and stats calls yourself.
• What to call next: gns_person_info or gns_league_leaderboards.

​

gns_phase_competition_pack

• What it helps you do: combine phase metadata and results in one call.
• When to use it: group-stage, round, knockout-pair, or matchday experiences.
• Inputs you need: phaseId, optional language.
• What you get back: phase info plus phase results.
• Example user questions it can answer: “What happened in this round or group?”
• Example request:

{
  "name": "gns_phase_competition_pack",
  "arguments": {
    "phaseId": "PHASE_ID",
    "language": "en-US"
  }
}

• Expected response summary: one compact object for a phase page or assistant answer.
• What to call next: gns_matchboard if the user opens a match from the returned phase context.

​

gns_overall_competition_pack

• What it helps you do: combine overall metadata and results in one call.
• When to use it: discipline-specific or gender-specific competition views, especially in sports that use overalls.
• Inputs you need: overallId, optional language.
• What you get back: overall info plus overall results.
• Example user questions it can answer: “Show me the results for this overall competition.”
• Example request:

{
  "name": "gns_overall_competition_pack",
  "arguments": {
    "overallId": "OVERALL_ID",
    "language": "en-US"
  }
}

• Expected response summary: a combined overall payload that works well for result-centric sports experiences.
• What to call next: gns_phase_competition_pack or the relevant participant profiles.

​

gns_historic_season_bundle

• What it helps you do: fetch one historic season bundle directly or resolve it from a current league.
• When to use it: retrospective pages, season archives, and assistant prompts like “show me the 2023 season.”
• Inputs you need: leagueSeasonId or leagueId, optional seasonSelector, optional include flags, optional language.
• What you get back: the selected historic season plus optional structure, standings, brackets, teams, and classifications.
• Example user questions it can answer: “Give me the latest completed historic season for this league.”
• Example request:

{
  "name": "gns_historic_season_bundle",
  "arguments": {
    "leagueId": "LEAGUE_ID",
    "seasonSelector": "latest",
    "language": "en-US"
  }
}

{
  "name": "gns_historic_season_bundle",
  "arguments": {
    "leagueSeasonId": "LEAGUE_SEASON_ID",
    "includeBrackets": true,
    "includeClassifications": true,
    "language": "en-US"
  }
}

• Expected response summary: one historic season envelope you can render or compare without manually resolving each section.
• What to call next: gns_season_compare or gns_team_season_profile.

​

gns_season_compare

• What it helps you do: compare two league seasons directly.
• When to use it: year-over-year analysis, editorial comparison, or AI answers about how a league changed.
• Inputs you need: leagueSeasonIdA, leagueSeasonIdB, optional language.
• What you get back: season A and season B side by side with standings, classifications, and teams.
• Example user questions it can answer: “Compare this season to last season.”
• Example request:

{
  "name": "gns_season_compare",
  "arguments": {
    "leagueSeasonIdA": "LEAGUE_SEASON_ID_A",
    "leagueSeasonIdB": "LEAGUE_SEASON_ID_B",
    "language": "en-US"
  }
}

• Expected response summary: a two-season comparison package that an LLM can reason over without extra joins.
• What to call next: your rendering or summarization layer.

​

gns_series_championship_snapshot

• What it helps you do: summarize a series or championship that spans multiple leagues.
• When to use it: championship tables, cross-league narratives, and motorsport-style flows.
• Inputs you need: seriesId or seriesSeasonId, optional topLeaguesLimit, optional language.
• What you get back: series info, league overview, and linked standings context for the top selected leagues.
• Example user questions it can answer: “What’s the championship picture across this series?”
• Example request:

{
  "name": "gns_series_championship_snapshot",
  "arguments": {
    "seriesId": "SERIES_ID",
    "topLeaguesLimit": 5,
    "language": "en-US"
  }
}

• Expected response summary: a championship snapshot that connects a series to the league standings that matter.
• What to call next: gns_live_league_dashboard or gns_historic_season_bundle for a specific league inside the series.

​

Bundle Notes