League and Series Tools

​

Start Here If

• you have a league or series ID and want real competition context
• you need standings, brackets, teams, or roster views
• you want to move between current-season and historic-season workflows safely
• you are building series or championship stories spanning multiple leagues

​

Scope Rule

• leagueId for the current season
• leagueSeasonId for a specific historic or explicit season

​

Tool Selection Guide

​

League Identity and Season Discovery

​

gns_get_league

• What it helps you do: inspect one league and confirm the sport and current season reference.
• When to use it: after gns_list_leagues or gns_resolve_entity.
• Inputs you need: leagueId, optional language.
• What you get back: league metadata, names, imagery, and current season reference.
• Example user questions it can answer: “What league is this ID?”
• Example request:

{
  "name": "gns_get_league",
  "arguments": {
    "leagueId": "LEAGUE_ID",
    "language": "en-US"
  }
}

• Expected response summary: one league record.
• What to call next: gns_league_structure, gns_league_standings, or gns_league_seasons.

​

gns_league_seasons

• What it helps you do: list the season catalog for a league.
• When to use it: historic lookups, comparison flows, or season selectors.
• Inputs you need: leagueId, optional language.
• What you get back: leagueSeasonId values, names, and date ranges.
• Example user questions it can answer: “Which seasons are available for this league?”
• Example request:

{
  "name": "gns_league_seasons",
  "arguments": {
    "leagueId": "LEAGUE_ID",
    "language": "en-US"
  }
}

• Expected response summary: a season list you can use in explicit historic workflows.
• What to call next: gns_get_league_season, gns_historic_season_bundle, or gns_season_compare.

​

gns_get_league_season

• What it helps you do: inspect one explicit league season.
• When to use it: the product already knows which season the user selected.
• Inputs you need: leagueSeasonId, optional language.
• What you get back: the selected season’s names, dates, and league context.
• Example user questions it can answer: “What season does this ID represent?”
• Example request:

{
  "name": "gns_get_league_season",
  "arguments": {
    "leagueSeasonId": "LEAGUE_SEASON_ID",
    "language": "en-US"
  }
}

• Expected response summary: one season record you can display or compare.
• What to call next: gns_league_structure, gns_league_standings, or gns_league_brackets.

​

Structure, Tables, and Competition Context

​

gns_league_structure

• What it helps you do: understand the structure of a competition before you build on top of it.
• When to use it: group-stage, bracket, conference, division, or phase-aware experiences.
• Inputs you need: leagueId or leagueSeasonId, optional language.
• What you get back: phases, groups, rounds, dates, and related sports-event IDs.
• Example user questions it can answer: “How is this competition organized?”
• Example request:

{
  "name": "gns_league_structure",
  "arguments": {
    "leagueId": "LEAGUE_ID",
    "language": "en-US"
  }
}

• Expected response summary: the structural map for the season, including IDs reused by standings and sports-event tools.
• What to call next: gns_league_standings, gns_league_brackets, gns_phase_info, or gns_overall_info.

​

gns_league_standings

• What it helps you do: answer standings questions for a league or a specific slice of it.
• When to use it: league tables, conference views, division views, or tier-specific standings.
• Inputs you need: leagueId or leagueSeasonId, plus optional conferenceId, divisionId, or tierId.
• What you get back: standings for the requested scope.
• Example user questions it can answer: “Show me the standings for this conference.”
• Example request:

{
  "name": "gns_league_standings",
  "arguments": {
    "leagueId": "LEAGUE_ID",
    "language": "en-US"
  }
}

{
  "name": "gns_league_standings",
  "arguments": {
    "leagueId": "LEAGUE_ID",
    "conferenceId": "CONFERENCE_ID",
    "language": "en-US"
  }
}

{
  "name": "gns_league_standings",
  "arguments": {
    "leagueSeasonId": "LEAGUE_SEASON_ID",
    "language": "en-US"
  }
}

• Expected response summary: a standings table for the requested slice of the competition.
• What to call next: gns_team_info, gns_team_season_profile, or gns_live_league_dashboard.

​

gns_league_brackets

• What it helps you do: retrieve knockout bracket context.
• When to use it: playoff pages, elimination rounds, or bracket-aware assistants.
• Inputs you need: leagueId or leagueSeasonId, optional language.
• What you get back: rounds, pairs, and matches for knockout competition.
• Example user questions it can answer: “Show me the playoff bracket.”
• Example request:

{
  "name": "gns_league_brackets",
  "arguments": {
    "leagueId": "LEAGUE_ID",
    "language": "en-US"
  }
}

• Expected response summary: bracket structure with match references.
• What to call next: gns_matchboard or gns_match_info.

​

gns_league_classifications

• What it helps you do: discover the stat categories available for a season.
• When to use it: leaderboards, top-scorer widgets, or stat tabs.
• Inputs you need: leagueId or leagueSeasonId, optional language.
• What you get back: classification IDs and names.
• Example user questions it can answer: “Which leaderboard categories are available for this league?”
• Example request:

{
  "name": "gns_league_classifications",
  "arguments": {
    "leagueId": "LEAGUE_ID",
    "language": "en-US"
  }
}

• Expected response summary: the classification catalog you can pass into classification or leaderboard tools.
• What to call next: gns_classification_results, gns_classification_info, or gns_league_leaderboards.

​

gns_league_tiers

• What it helps you do: discover tier structures within a league.
• When to use it: college sports or competitions where tier is a meaningful filter.
• Inputs you need: leagueId or leagueSeasonId, optional language.
• What you get back: tier IDs and names.
• Example user questions it can answer: “Which tiers exist in this competition?”
• Example request:

{
  "name": "gns_league_tiers",
  "arguments": {
    "leagueId": "LEAGUE_ID",
    "language": "en-US"
  }
}

• Expected response summary: a tier list you can reuse in standings and schedule filters.
• What to call next: gns_league_standings or gns_schedule_results with tierId.

​

Teams, Rosters, and Season Stats

​

gns_league_teams

• What it helps you do: list teams in a league or season.
• When to use it: team pickers, league hubs, or roster flows.
• Inputs you need: leagueId or leagueSeasonId, optional language.
• What you get back: team IDs, names, images, and type.
• Example user questions it can answer: “Which teams are in this league?”
• Example request:

{
  "name": "gns_league_teams",
  "arguments": {
    "leagueId": "LEAGUE_ID",
    "language": "en-US"
  }
}

• Expected response summary: a team catalog for the selected season context.
• What to call next: gns_team_roster, gns_team_info, or gns_team_season_profile.

​

gns_team_roster

• What it helps you do: fetch a roster for one team in one league-season context.
• When to use it: team pages, lineup prep, or player discovery flows.
• Inputs you need: teamId and either leagueId or leagueSeasonId.
• What you get back: players, coaches, positions, and jersey numbers.
• Example user questions it can answer: “Who is on this roster?”
• Example request:

{
  "name": "gns_team_roster",
  "arguments": {
    "leagueId": "LEAGUE_ID",
    "teamId": "TEAM_ID",
    "language": "en-US"
  }
}

• Expected response summary: a roster you can reuse in match, player-profile, and team-season experiences.
• What to call next: gns_person_info, gns_person_league_stats, or gns_team_season_profile.

​

gns_team_league_stats

• What it helps you do: fetch season stats for one team in one league context.
• When to use it: team hubs, standings explainers, or season comparison features.
• Inputs you need: teamId and either leagueId or leagueSeasonId.
• What you get back: aggregated team statistics for the season.
• Example user questions it can answer: “How is this team performing this season?”
• Example request:

{
  "name": "gns_team_league_stats",
  "arguments": {
    "leagueId": "LEAGUE_ID",
    "teamId": "TEAM_ID",
    "language": "en-US"
  }
}

• Expected response summary: season-long team stats categories and values.
• What to call next: gns_team_season_profile or your summary layer.

​

gns_person_league_stats

• What it helps you do: fetch season stats for one person in one league context.
• When to use it: player pages, leaderboard explanations, or scouting-style summaries.
• Inputs you need: personId and either leagueId or leagueSeasonId.
• What you get back: aggregated person stats for the season.
• Example user questions it can answer: “How has this player performed this season?”
• Example request:

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

• Expected response summary: one person’s season stats in the requested league context.
• What to call next: gns_person_season_profile or gns_person_info.

​

Series Context

​

gns_get_series

• What it helps you do: inspect one series or championship grouping.
• When to use it: motorsport or other multi-league championship workflows.
• Inputs you need: seriesId, optional language.
• What you get back: series metadata and sport association.
• Example user questions it can answer: “What series is this ID?”
• Example request:

{
  "name": "gns_get_series",
  "arguments": {
    "seriesId": "SERIES_ID",
    "language": "en-US"
  }
}

• Expected response summary: one series record.
• What to call next: gns_series_seasons or gns_series_league_overview.

​

gns_series_seasons

• What it helps you do: list seasons for a series.
• When to use it: historic series views and series selectors.
• Inputs you need: seriesId, optional language.
• What you get back: series-season IDs, names, and dates.
• Example user questions it can answer: “Which seasons exist for this series?”
• Example request:

{
  "name": "gns_series_seasons",
  "arguments": {
    "seriesId": "SERIES_ID",
    "language": "en-US"
  }
}

• Expected response summary: season catalog for the selected series.
• What to call next: gns_get_series_season or gns_series_championship_snapshot.

​

gns_get_series_season

• What it helps you do: inspect one explicit series season.
• When to use it: series history or selected-season views.
• Inputs you need: seriesSeasonId, optional language.
• What you get back: one series-season record with names and dates.
• Example user questions it can answer: “What series season is this?”
• Example request:

{
  "name": "gns_get_series_season",
  "arguments": {
    "seriesSeasonId": "SERIES_SEASON_ID",
    "language": "en-US"
  }
}

• Expected response summary: one series-season record.
• What to call next: gns_series_league_overview.

​

gns_series_league_overview

• What it helps you do: see which leagues make up a series.
• When to use it: championship overviews or cross-league assistant flows.
• Inputs you need: seriesId or seriesSeasonId, optional language.
• What you get back: leagues and league-season references inside the series.
• Example user questions it can answer: “Which leagues feed into this series?”
• Example request:

{
  "name": "gns_series_league_overview",
  "arguments": {
    "seriesId": "SERIES_ID",
    "language": "en-US"
  }
}

{
  "name": "gns_series_league_overview",
  "arguments": {
    "seriesSeasonId": "SERIES_SEASON_ID",
    "language": "en-US"
  }
}

• Expected response summary: the leagues and seasons tied to the series.
• What to call next: gns_series_championship_snapshot or league tools for one returned league.

​

Recommended Pattern