Product Outcome
Deliver a live sports surface that can answer questions like what is on now, what is final, what starts next, and which league or sport a user should drill into next.Who Builds This
- AI product teams shipping fan-facing assistants
- editorial and content operations teams
- mobile, web, and connected-TV teams
- internal agents that need fresh daily sports context
Recommended Tool Chain
| Step | Tool | Why it matters |
|---|---|---|
| 1 | gns_list_sports or gns_list_leagues | confirm the catalog you can cover |
| 2 | gns_resolve_entity | map a fuzzy league or team name to a canonical ID |
| 3 | gns_schedule_results | fetch a targeted live or near-live window |
| 4 | gns_sports_dayboard | produce a compact cross-sport scoreboard |
| 5 | gns_live_league_dashboard | enrich a specific league view with standings and structure |
Minimum Inputs
- a date or time window
- optionally a
sportIdorleagueId - optionally a canonical ID for the league or team the user is asking about
Example End-User Prompts
- “What games are on tonight across soccer and basketball?”
- “Show me today’s Premier League matches.”
- “Which match just went final?”
- “What should I pin to the top of a live scoreboard right now?”
Expected Output / UX
The best scoreboard experiences usually show:- current or upcoming matches in the requested window
- scores, status, and start times
- obvious drill-down paths into a league dashboard or match center
- consistent naming and identifiers the rest of your product can reuse
Common Mistakes
- starting from free-text league names without resolving them first
- building a cross-sport scoreboard out of deep match tools instead of schedule tools
- over-fetching live detail before the user has chosen a match worth opening
- forgetting to bound the time window for daily or weekly experiences