Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.etonecarg.com/llms.txt

Use this file to discover all available pages before exploring further.

Canonical tool name: get_competition_hub Family: Hybrid Bundle Tools

What this tool is best at

Return structure, schedule, standings, rankings, and optional watchable rail for one competition scope.

Choose this tool when

  • the product needs one coherent competition surface instead of stitching multiple calls together.
  • Source ownership: GSD Lookup primary, availability overlay optional

Use something smaller or different when

  • the host only needs a single atomic section like standings or a single schedule list.

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

InputWhat it means
timeFromBounded window start. Use an ISO date or timestamp that matches the user’s browse moment or watchability horizon. Some tools require this field as part of the public contract.
timeToBounded window end. Keep it tight enough that the request still represents one real product moment. Some tools require this field as part of the public contract.

Optional inputs in the public contract

InputWhat it means
competitionIdCompetition ref for the selected competition scope. Use the best provider-facing ref you preserved from the resolving step.
competitionSeasonIdSeason-specific competition ref when the UX is centered on one season rather than the broader competition.
includeSectionsOptional section allow-list for bundle tools. Use it when the host wants one composed tool but still needs a bounded payload.
rowLimitOptional cap for repeated rows returned inside bundles such as hubs or event-center watchability sections.
languageOptional BCP 47 language hint such as en-US. Use it when the host needs translated provider output.

Sequencing guidance

Needed ID or scopeCall this firstThen use
competition scoperesolve_entitiesCarry the best provider ref into get_competition_hub, then branch into atomic tools only if the user drills down.

Response highlights

  • Return structure, schedule, standings, rankings, and optional watchable rail for one competition scope.

Response shape

FieldWhat it means
data.structureCompetition structure or season structure block.
data.items[]Bounded schedule preview rows.
data.standings / data.standingsRows[] / data.standingsGroups[]Standings payload plus normalized preview rows and grouped slices.
data.rankingRefsActionable overallRefs and classificationRefs for later ranking calls.
data.rankingPreview[]Preview leaderboard rows chosen from the best non-empty ranking selection.
data.watchability[]Optional bounded watchability rail for the selected competition scope.
data.watchabilityAvailabilityModeOverall watchability mode for the competition hub preview.

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_competition_hub when the host already knows the right scope and needs this job directly.

Common mistakes

  • Treating it like a compare tool. For comparisons, call the hub multiple times and compare in the client or agent.