Get Event Center

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

Input	What it means
`eventId`	Event ref for the selected event-center experience.
`timeFrom`	Bounded window start for the watchability-aware sections inside the bundle.
`timeTo`	Bounded window end for the watchability-aware sections inside the bundle.

Optional inputs in the public contract

Input	What it means
`idSource`	Lookup-path hint for the supplied ID. `auto` uses namespace-aware routing, `gsd` treats the ID as sports-truth-facing, and `on` treats it as On-facing. It does not change source-of-truth ownership.
`includeLineups`	Include lineups and officials in the event-center bundle.
`includeTimeline`	Include play-by-play, incidents, or event-action timeline data in the bundle.
`includeStats`	Include event stats in the bundle.
`includeOdds`	Include odds data when available.
`includeWatchOptions`	Include watchability enrichment in the bundle.
`includeMedia`	Include bounded media and imagery enrichment in the bundle.
`includeEditorial`	Include editorial enrichment when the experience truly needs it. Leave it off for tighter default responses.
`includeSections`	Optional section allow-list for bundle tools. Use it when the host wants one composed tool but still needs a bounded payload.
`rowLimit`	Optional cap for repeated rows returned inside bundles such as hubs or event-center watchability sections.
`language`	Optional BCP 47 language hint such as `en-US`. Use it when the host needs translated provider output.

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

Needed ID or scope	Call this first	Then use
scope	Tool Catalog	Start from the smallest tool that can safely anchor the workflow, then deepen only if the user asks for more.

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

Field	What it means
`data.summary`	Minimum event summary block for the selected event.
`data.lineups`	Optional lineup and official block.
`data.timeline`	Optional action or play-by-play block.
`data.stats`	Optional stats bundle containing `teamStats` and `personStats` plus normalized groups.
`data.odds`	Optional odds block.
`data.watchAvailability`	Optional watchability bundle with `options[]`, `eventEvidence[]`, `linkageStatus`, and `availabilityMode`.
`data.media / data.editorial`	Optional bounded media and editorial enrichment blocks.
`meta.partial / meta.missingSections[] / meta.limitations[]`	Envelope-level signals for requested sections that were intentionally omitted or unavailable.

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

Recommended request
Expanded request

{
  "jsonrpc": "2.0",
  "id": "tool-call-1",
  "method": "tools/call",
  "params": {
    "name": "get_event_center",
    "arguments": {
      "eventId": "MATCH_ID",
      "timeFrom": "2026-04-08T18:00:00Z",
      "timeTo": "2026-04-08T23:00:00Z",
      "includeEditorial": false
    }
  }
}

{
  "jsonrpc": "2.0",
  "id": "tool-call-1",
  "method": "tools/call",
  "params": {
    "name": "get_event_center",
    "arguments": {
      "eventId": "MATCH_ID",
      "timeFrom": "2026-04-08T18:00:00Z",
      "timeTo": "2026-04-08T23:00:00Z",
      "includeLineups": true,
      "includeTimeline": true,
      "includeStats": true,
      "includeOdds": true,
      "includeWatchOptions": true,
      "includeMedia": true,
      "includeEditorial": true
    }
  }
}

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.

Getting Started

Concepts

Guides

Tools

Tool Reference

Reference

What this tool is best at

Choose this tool when

Use something smaller or different when

Inputs you need

Plain-English prerequisites

Required inputs in the public contract

Optional inputs in the public contract

Notes on optional inputs

Sequencing guidance

Response highlights

Response shape

Reuse next

Example requests

Previous-step tools

Next-step tools

Alternative tools

Prompt patterns this tool fits

Common mistakes

Getting Started

Concepts

Guides

Tools

Tool Reference

Reference

Documentation Index

​What this tool is best at

​Choose this tool when

​Use something smaller or different when

​Inputs you need

​Plain-English prerequisites

​Required inputs in the public contract

​Optional inputs in the public contract

​Notes on optional inputs

​Sequencing guidance

​Response highlights

​Response shape

​Reuse next

​Example requests

​Related tools

​Previous-step tools

​Next-step tools

​Alternative tools

​Prompt patterns this tool fits

​Common mistakes

What this tool is best at

Choose this tool when

Use something smaller or different when

Inputs you need

Plain-English prerequisites

Required inputs in the public contract

Optional inputs in the public contract

Notes on optional inputs

Sequencing guidance

Response highlights

Response shape

Reuse next

Example requests

Related tools

Previous-step tools

Next-step tools

Alternative tools

Prompt patterns this tool fits

Common mistakes