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_venue_profile Family: Deep Sports Truth Tools

What this tool is best at

Return venue identity, geography, timezone, and normalized refs.

Choose this tool when

  • the product needs venue context, travel/location framing, or venue-linked watchability browse flows.
  • Source ownership: On Sports Venues primary, GSD enrichment optional

Use something smaller or different when

  • the answer is really about a competition, team, or event instead.

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
venueIdProvider ref for one venue. Use it when the workflow is venue-led or when the schedule/watchability row already exposed the venue.

Optional inputs in the public contract

InputWhat it means
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
scopeTool CatalogStart from the smallest tool that can safely anchor the workflow, then deepen only if the user asks for more.

Response highlights

  • Return venue identity, geography, timezone, and normalized refs.

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

{
  "jsonrpc": "2.0",
  "id": "tool-call-1",
  "method": "tools/call",
  "params": {
    "name": "get_venue_profile",
    "arguments": {
      "venueId": "VENUE_ID"
    }
  }
}

Previous-step tools

Next-step tools

Alternative tools

  • No common alternatives.

Prompt patterns this tool fits

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

Common mistakes

  • Calling get_venue_profile before the host has the right provider refs or bounded window.
  • Using get_venue_profile when a smaller sibling tool would answer the question more directly.