Skip to main content

Quickstart

The fastest path to a successful integration is:
  1. resolve scope only when the prompt is ambiguous
  2. choose whether the job is competition-first or availability-first
  3. deepen only when the user actually needs more detail

Pick the right first path

Start with resolve_entities when the prompt is fuzzy and your host does not yet know which competition, participant, venue, or program the user means.

Then choose the right schedule path

Use this when the user is asking about fixtures, rounds, matchups, or the sports calendar itself.

Open a single event only when needed

Use get_event_center when the product truly benefits from one coherent bundle.

Quick rules

  • Keep windows bounded.
  • Preserve provider refs exactly as they came back.
  • Treat partial, missingSections, and limitations as first-class workflow signals.
  • Prefer atomic tools unless the product clearly benefits from a hybrid bundle.

Read this next