Match, Participant, and Event Tools

​

Start Here If

• you already know the matchId, teamId, personId, phaseId, overallId, or classificationId
• the product needs lineups, actions, stats, odds, or competition results
• you are building a profile, match page, or results-heavy sports experience

​

Tool Selection Guide

​

Match Tools

​

gns_match_info

• What it helps you do: fetch the canonical match record.
• When to use it: you need participants, date, venue, status, scores, and winner information.
• Inputs you need: matchId, optional language.
• What you get back: detailed match metadata.
• Example user questions it can answer: “What match does this ID represent?”
• Example request:

{
  "name": "gns_match_info",
  "arguments": {
    "matchId": "MATCH_ID",
    "language": "en-US"
  }
}

• Expected response summary: one match object you can use as the anchor for a match-center workflow.
• What to call next: gns_match_lineups, gns_match_actions, or gns_matchboard.

​

gns_match_lineups

• What it helps you do: fetch the people context around a match.
• When to use it: starting lineups, substitutions, coaches, or officials matter to the product.
• Inputs you need: matchId, optional language.
• What you get back: lineup and personnel data for both sides.
• Example user questions it can answer: “Who started this match?”
• Example request:

{
  "name": "gns_match_lineups",
  "arguments": {
    "matchId": "MATCH_ID",
    "language": "en-US"
  }
}

• Expected response summary: lineups and related person IDs you can reuse in person-profile flows.
• What to call next: gns_person_info, gns_matchboard, or gns_match_tactical_view.

​

gns_match_actions

• What it helps you do: retrieve the play-by-play or event timeline of a match.
• When to use it: live blogs, recap agents, tactical explainers, or event timelines.
• Inputs you need: matchId, optional tags, optional language.
• What you get back: ordered actions with timestamps and event metadata.
• Example user questions it can answer: “What happened in this match?”
• Example request:

{
  "name": "gns_match_actions",
  "arguments": {
    "matchId": "MATCH_ID",
    "tags": "main",
    "language": "en-US"
  }
}

• Expected response summary: a timeline of actions, optionally narrowed to the most important event types.
• What to call next: gns_match_tactical_view or your recap prompt.

​

gns_match_team_stats

• What it helps you do: compare team-level performance inside one match.
• When to use it: possession, shots, fouls, and other aggregate match stats matter.
• Inputs you need: matchId, optional language.
• What you get back: team stats and stat classifications.
• Example user questions it can answer: “How did the teams compare statistically?”
• Example request:

{
  "name": "gns_match_team_stats",
  "arguments": {
    "matchId": "MATCH_ID",
    "language": "en-US"
  }
}

• Expected response summary: per-team statistical totals for the match.
• What to call next: gns_matchboard or your analytics layer.

​

gns_match_person_stats

• What it helps you do: inspect player-by-player statistical performance inside one match.
• When to use it: player ratings, recaps, or stat-detail tabs matter.
• Inputs you need: matchId, optional language.
• What you get back: individual player stats and classifications.
• Example user questions it can answer: “Which players stood out statistically?”
• Example request:

{
  "name": "gns_match_person_stats",
  "arguments": {
    "matchId": "MATCH_ID",
    "language": "en-US"
  }
}

• Expected response summary: player-level statistical rows.
• What to call next: gns_person_info or your ranking and summary layer.

​

gns_match_odds

• What it helps you do: fetch betting-market context for a match when available.
• When to use it: odds cards, probabilities, or market-aware assistant responses matter.
• Inputs you need: matchId, optional language.
• What you get back: odds and probability-related market data.
• Example user questions it can answer: “What were the odds for this match?”
• Example request:

{
  "name": "gns_match_odds",
  "arguments": {
    "matchId": "MATCH_ID",
    "language": "en-US"
  }
}

• Expected response summary: one match’s available market context.
• What to call next: gns_matchboard if you want the broader match-center envelope.

​

Participant Tools

​

gns_team_info

• What it helps you do: inspect one team profile.
• When to use it: team cards, team pages, or any product needing canonical team metadata.
• Inputs you need: teamId, optional language.
• What you get back: team names, imagery, type, and nationality.
• Example user questions it can answer: “Tell me about this team.”
• Example request:

{
  "name": "gns_team_info",
  "arguments": {
    "teamId": "TEAM_ID",
    "language": "en-US"
  }
}

• Expected response summary: one team record that can anchor schedule, roster, and season flows.
• What to call next: gns_team_schedule_results, gns_team_roster, or gns_team_season_profile.

​

gns_person_info

• What it helps you do: inspect one person profile.
• When to use it: player cards, person pages, or human-readable roster experiences.
• Inputs you need: personId, optional language.
• What you get back: person metadata including nationality, gender, and physical details where available.
• Example user questions it can answer: “Who is this player?”
• Example request:

{
  "name": "gns_person_info",
  "arguments": {
    "personId": "PERSON_ID",
    "language": "en-US"
  }
}

• Expected response summary: one person record.
• What to call next: gns_person_league_stats or gns_person_season_profile.

​

Sports Event Tools

​

gns_overall_info

• What it helps you do: inspect an overall such as a discipline-gender combination.
• When to use it: sports where a season or event is organized around overalls.
• Inputs you need: overallId, optional language.
• What you get back: overall metadata, status, dates, and related events.
• Example user questions it can answer: “What overall competition is this?”
• Example request:

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

• Expected response summary: one overall record.
• What to call next: gns_overall_results or gns_overall_competition_pack.

​

gns_overall_results

• What it helps you do: fetch ranked results for an overall.
• When to use it: result-centric sports flows or overall standings.
• Inputs you need: overallId, optional language.
• What you get back: participant results, rankings, times, scores, or stats for the overall.
• Example user questions it can answer: “Who won this overall competition?”
• Example request:

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

• Expected response summary: result rows for the selected overall.
• What to call next: gns_overall_competition_pack.

​

gns_phase_info

• What it helps you do: inspect one competition phase such as a round, group, pair, or matchday.
• When to use it: phase pages or phase-aware assistant answers.
• Inputs you need: phaseId, optional language.
• What you get back: phase metadata, type, dates, and related sports events.
• Example user questions it can answer: “What phase is this?”
• Example request:

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

• Expected response summary: one phase record.
• What to call next: gns_phase_results or gns_phase_competition_pack.

​

gns_phase_results

• What it helps you do: fetch results for a single phase.
• When to use it: group-stage, round, or pair-result experiences.
• Inputs you need: phaseId, optional language.
• What you get back: participant results and rankings for that phase.
• Example user questions it can answer: “What were the results of this round?”
• Example request:

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

• Expected response summary: ranked results for the phase.
• What to call next: gns_phase_competition_pack.

​

gns_classification_info

• What it helps you do: inspect a classification definition.
• When to use it: leaderboard UIs or stat-category selectors.
• Inputs you need: classificationId, optional language.
• What you get back: classification metadata such as stat key and sort behavior.
• Example user questions it can answer: “What stat category is this?”
• Example request:

{
  "name": "gns_classification_info",
  "arguments": {
    "classificationId": "CLASSIFICATION_ID",
    "language": "en-US"
  }
}

• Expected response summary: one classification definition.
• What to call next: gns_classification_results or gns_league_leaderboards.

​

gns_classification_results

• What it helps you do: fetch the ranked participants for a classification.
• When to use it: top-scorer tables, assists leaders, and similar ranked stat views.
• Inputs you need: classificationId, optional language.
• What you get back: ranked participant results.
• Example user questions it can answer: “Who leads this category?”
• Example request:

{
  "name": "gns_classification_results",
  "arguments": {
    "classificationId": "CLASSIFICATION_ID",
    "language": "en-US"
  }
}

• Expected response summary: the ranked results for that classification.
• What to call next: gns_person_info or gns_person_season_profile.

​

gns_organization_info

• What it helps you do: inspect a tier, conference, or division.
• When to use it: filtered standings, organizational structure, or human-readable labels for grouped competition contexts.
• Inputs you need: type, id, optional language.
• What you get back: the selected organization’s metadata.
• Example user questions it can answer: “What conference or division is this?”
• Example request:

{
  "name": "gns_organization_info",
  "arguments": {
    "type": "conference",
    "id": "CONFERENCE_ID",
    "language": "en-US"
  }
}

• Expected response summary: one tier, conference, or division record.
• What to call next: gns_league_standings or gns_live_league_dashboard with the same organization ID.

​

Recommended Pattern