Sequencing habits
- Use bundles only when the product benefits from one coherent surface.
- Read
partial,missingSections, andlimitationsbefore rendering as complete.
Decision guide
Tool-by-tool guidance
get_competition_hub
- Job: Return structure, schedule, standings, rankings, and optional watchable rail for one competition scope.
- Source ownership: GSD Lookup primary, availability overlay optional
- Use it when: the product needs one coherent competition surface instead of stitching multiple calls together.
- Do not use it when: the host only needs a single atomic section like standings or a single schedule list.
get_series_hub
- Job: Return one compact series bundle with series seasons, bounded event rows, leaderboard refs, and phase refs for tours and motorsports.
- Source ownership: GSD Lookup primary
- Use it when: the product needs one tour or series surface instead of stitching schedule, rankings, and phase discovery together.
- Do not use it when: the host only needs a single schedule list, one leaderboard, or one phase/session result slice.
get_event_center
- Job: Return the main one-call event recap bundle with summary, optional lineups, optional timeline, optional stats, optional odds, optional watchability, optional media, and optional editorial.
- Source ownership: GSD Lookup primary, availability optional, GSD Metadata media/editorial optional
- Use it when: the product wants the event center in one response instead of calling summary, lineups, timeline, stats, odds, watchability, and media separately.
- Do not use it when: the host only needs one atomic event section or when the extra sections would waste tokens.
Next steps
- Use Tool Catalog when you want the full 1.4.1 surface in one place.
- Use ID Acquisition and Tool Sequencing when the host still needs provider refs or a safer tool order.
- Use Prompt-to-Tool Mapping when you want a proven low-token workflow for a real user prompt.