Product Outcome
Ship season snapshots and historical comparisons without manually composing multiple standings, team, classification, and structure calls for every query.Who Builds This
- editorial retrospectives and season reviews
- AI assistants that compare eras or years
- historical league, team, or player experiences
- product teams that want one-call season bundles
Recommended Tool Chain
| Step | Tool | Why it matters |
|---|---|---|
| 1 | gns_league_seasons | discover the season IDs you can compare |
| 2 | gns_league_season_snapshot | get a broad current or explicit season package |
| 3 | gns_historic_season_bundle | fetch one historic season with optional sections |
| 4 | gns_season_compare | compare two league seasons directly |
| 5 | gns_series_championship_snapshot | summarize championship context across leagues |
Minimum Inputs
leagueIdwhen you want to resolve a season from the current leagueleagueSeasonIdwhen you already know the exact seasonseriesIdorseriesSeasonIdfor championship snapshots
Example End-User Prompts
- “Compare this season with last season.”
- “Build a season snapshot for the 2023 campaign.”
- “Who led the league in key categories that year?”
- “Give me the championship picture across the leagues in this series.”
Expected Output / UX
Strong historical experiences give the user:- a clear season identity and date range
- standings, structure, teams, and classifications in one place
- an explicit comparison frame rather than raw data dumps
- a path from league-season context into team or person profiles
Common Mistakes
- comparing a current
leagueIdresponse with a historicleagueSeasonIdresponse without normalizing scope - requesting every optional section when the use case needs only one or two
- treating
latestas a fixed season instead of a moving selector