Live Bundle Tools

​

Start Here If

• you want a match center in one call
• you need a tactical or timeline-oriented match view
• you want a live league dashboard with standings and schedule together
• you want a team dashboard or a cross-sport dayboard

​

Tool Selection Guide

​

gns_matchboard

• What it helps you do: build a match center in one call.
• When to use it: the user selected a match and you want match info plus optional lineups, actions, stats, and odds.
• Inputs you need: matchId, optional include flags, optional actionTags, optional language.
• What you get back: a bundled envelope with the requested match sections.
• Example user questions it can answer: “Show me everything I need for a live match page.”
• Example request:

{
  "name": "gns_matchboard",
  "arguments": {
    "matchId": "MATCH_ID",
    "includeLineups": true,
    "includeActions": true,
    "includeTeamStats": true,
    "includePersonStats": false,
    "includeOdds": false,
    "language": "en-US"
  }
}

• Expected response summary: one bundled match envelope suitable for a live center or recap experience.
• What to call next: usually nothing deeper unless you want more specialized match analysis.

​

gns_match_tactical_view

• What it helps you do: create an action-first tactical or timeline view.
• When to use it: the product values event flow more than broad match metadata.
• Inputs you need: matchId, optional actionTags, optional windowMinutes, optional language.
• What you get back: match info plus a bounded tactical timeline, lineups, and team stats.
• Example user questions it can answer: “Give me the key tactical story of this match.”
• Example request:

{
  "name": "gns_match_tactical_view",
  "arguments": {
    "matchId": "MATCH_ID",
    "actionTags": "main",
    "windowMinutes": 90,
    "language": "en-US"
  }
}

• Expected response summary: a timeline-oriented payload that is easier to summarize for an AI recap or tactical explainer.
• What to call next: gns_matchboard if you later need broader match context.

​

gns_live_league_dashboard

• What it helps you do: build a current league hub with structure, schedule, and standings in one response.
• When to use it: league homepages, assistants answering league-wide live questions, and scoreboards with table context.
• Inputs you need: leagueId or leagueSeasonId, timeFrom, timeTo, optional conferenceId, divisionId, tierId, optional language.
• What you get back: bundled league structure, live schedule window, and standings slice.
• Example user questions it can answer: “Give me today’s league dashboard with standings.”
• Example request:

{
  "name": "gns_live_league_dashboard",
  "arguments": {
    "leagueId": "LEAGUE_ID",
    "timeFrom": "2026-03-18",
    "timeTo": "2026-03-20",
    "language": "en-US"
  }
}

{
  "name": "gns_live_league_dashboard",
  "arguments": {
    "leagueId": "LEAGUE_ID",
    "conferenceId": "CONFERENCE_ID",
    "timeFrom": "2026-03-18",
    "timeTo": "2026-03-20",
    "language": "en-US"
  }
}

• Expected response summary: a one-call league dashboard that already knows the season structure and the relevant standings slice.
• What to call next: gns_matchboard if the user drills into a specific match.

​

gns_live_team_dashboard

• What it helps you do: build a team dashboard with identity, schedule, and optional season stats.
• When to use it: team homepages, follow feeds, and assistant responses about one team.
• Inputs you need: teamId, timeFrom, timeTo, and optionally leagueId or leagueSeasonId.
• What you get back: bundled team info, schedule, and optional season stats.
• Example user questions it can answer: “Give me a live view of this team right now.”
• Example request:

{
  "name": "gns_live_team_dashboard",
  "arguments": {
    "teamId": "TEAM_ID",
    "leagueId": "LEAGUE_ID",
    "timeFrom": "2026-03-18",
    "timeTo": "2026-03-31",
    "language": "en-US"
  }
}

• Expected response summary: team identity plus recent and upcoming matches, with season stats when league context is provided.
• What to call next: gns_team_season_profile if the product shifts from live view to season view.

​

gns_sports_dayboard

• What it helps you do: build a compact scoreboard across all sports or one sport.
• When to use it: homepages, “what’s on now” modules, or broad daily AI answers.
• Inputs you need: timeFrom, timeTo, optional sportId, optional maxMatches, optional language.
• What you get back: a bounded set of matches plus the raw schedule context.
• Example user questions it can answer: “What should I show on today’s sports homepage?”
• Example request:

{
  "name": "gns_sports_dayboard",
  "arguments": {
    "timeFrom": "2026-03-18",
    "timeTo": "2026-03-19",
    "maxMatches": 20,
    "language": "en-US"
  }
}

{
  "name": "gns_sports_dayboard",
  "arguments": {
    "sportId": "SPORT_ID",
    "timeFrom": "2026-03-18",
    "timeTo": "2026-03-19",
    "maxMatches": 20,
    "language": "en-US"
  }
}

• Expected response summary: a compact, bounded scoreboard that works well for daily surfaces and assistant summaries.
• What to call next: gns_live_league_dashboard or gns_matchboard depending on which card the user opens.

​

Bundle Notes