| Fuzzy resolution and scoping | resolve_entities | Resolve the right competition, series, participant, venue, or program before deeper calls. |
| Competition-first schedule truth | list_schedule | Stay in GSD when the question is about the sports calendar rather than watchability. |
| Watchable schedule or live slate | list_watchable_schedule, list_live_slate | Lead with the dedicated availability contract for grounded where-to-watch answers, then fall back to sports truth only when availability is not provisioned. |
| One event with optional watchability | get_event_summary, get_event_center | Start small for deep truth, then bundle only when the experience needs it. |
| Competition dashboard | get_competition_hub | Use one hybrid hub when the product needs structure, standings, schedule, and optional availability together. |
| Tour or motorsport hub | get_series_hub | Use one series bundle when the product needs tour context, leaderboard refs, and bounded event rows together. |
| Phase or session results | get_phase_results | Deepen from a known phase when the question is about qualifying, rounds, heats, or other staged slices. |
| Program linkage or program-first flows | list_programs_for_entity, get_program_context | Keep raw evidence and normalized program context separate. |