Skip to main content
Canonical tool name: get_event_center Family: Hybrid Bundle Tools

What this tool is best at

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.

Choose this tool when

  • the product wants the event center in one response instead of calling summary, lineups, timeline, stats, odds, watchability, and media separately.
  • Source ownership: GSD Lookup primary, availability optional, GSD Metadata media/editorial optional

Use something smaller or different when

  • the host only needs one atomic event section or when the extra sections would waste tokens.

Inputs you need

Plain-English prerequisites

  • This tool does not require a prerequisite ID beyond the scoped inputs shown below.

Required inputs in the public contract

Optional inputs in the public contract

Notes on optional inputs

  • includeSections overrides the individual boolean include flags when both are provided.
  • timeFrom and timeTo are still required even for one known event because watchability-aware sections are window-bound.

Sequencing guidance

  • Use this only after the host already knows the correct event.
  • Start from get_event_summary instead when the UX does not need the full bundle.

Response highlights

  • This is the main one-call event recap bundle, not a raw passthrough of every upstream event endpoint.
  • The bundle is section-bounded and may return partial success with explicit meta.partial, meta.missingSections[], and meta.limitations[] when one requested section is unavailable.

Response shape

Reuse next

  • Reuse provider refs returned by this tool to avoid resolving the same entity again.
  • Read meta.agentHints.recommendedNextTools and meta.agentHints.disambiguationOptions as non-binding host hints.

Example requests

Previous-step tools

Next-step tools

Alternative tools

  • No common alternatives.

Prompt patterns this tool fits

  • Use get_event_center when the host already knows the right scope and needs this job directly.

Common mistakes

  • Turning on every optional section by default when a smaller response would answer the prompt just as well.