> ## 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.

# Get Odds

> Return event odds when available.

Canonical tool name: `get_odds`

Family: [Deep Sports Truth Tools](/sports-mcp-server/tools/deep-sports-truth-tools)

## What this tool is best at

Return event odds when available.

## Choose this tool when

* the product explicitly needs odds or betting-style implied probability context.
* Source ownership: GSD Lookup

## Use something smaller or different when

* Do not use it for non-odds sports workflows or as a fallback when odds are missing.

## 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` | Provider ref for one event. Prefer the GSD-facing event ref for deep-sports tools and the selected event row for hybrid follow-ons. |

### 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. |
| `language` | Optional BCP 47 language hint such as `en-US`. Use it when the host needs translated provider output.                                                                                                 |

## Sequencing guidance

| Needed ID or scope | Call this first                                       | Then use                                                                                                      |
| ------------------ | ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- |
| scope              | [Tool Catalog](/sports-mcp-server/tools/tool-catalog) | Start from the smallest tool that can safely anchor the workflow, then deepen only if the user asks for more. |

## Response highlights

* Return event odds when available.

## 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

<CodeGroup>
  ```json JSON-RPC theme={null}
  {
    "jsonrpc": "2.0",
    "id": "tool-call-1",
    "method": "tools/call",
    "params": {
      "name": "get_odds",
      "arguments": {
        "eventId": "MATCH_ID"
      }
    }
  }
  ```

  ```bash curl theme={null}
  curl "https://sports-mcp-server.etonecarg.com/" \
    -X POST \
    -H "Authorization: Bearer $SPORTS_MCP_API_KEY" \
    -H "Accept: application/json, text/event-stream" \
    -H "Content-Type: application/json" \
    -H "mcp-protocol-version: 2025-03-26" \
    -d '{
    "jsonrpc": "2.0",
    "id": "tool-call-1",
    "method": "tools/call",
    "params": {
      "name": "get_odds",
      "arguments": {
        "eventId": "MATCH_ID"
      }
    }
  }'
  ```

  ```ts TypeScript theme={null}
  const payload = {
      "jsonrpc": "2.0",
      "id": "tool-call-1",
      "method": "tools/call",
      "params": {
        "name": "get_odds",
        "arguments": {
          "eventId": "MATCH_ID"
        }
      }
    };

  const response = await fetch("https://sports-mcp-server.etonecarg.com/", {
    method: "POST",
    headers: {
      Authorization: `Bearer ${process.env.SPORTS_MCP_API_KEY!}`,
      Accept: "application/json, text/event-stream",
      "Content-Type": "application/json",
      "mcp-protocol-version": "2025-03-26",
    },
    body: JSON.stringify(payload),
  });

  const data = await response.json();
  console.log(JSON.stringify(data, null, 2));
  ```

  ```python Python theme={null}
  import json
  import os

  import requests

  payload = {
    "jsonrpc": "2.0",
    "id": "tool-call-1",
    "method": "tools/call",
    "params": {
      "name": "get_odds",
      "arguments": {
        "eventId": "MATCH_ID"
      }
    }
  }

  response = requests.post(
      "https://sports-mcp-server.etonecarg.com/",
      headers={
          "Authorization": f"Bearer {os.environ['SPORTS_MCP_API_KEY']}",
          "Accept": "application/json, text/event-stream",
          "Content-Type": "application/json",
          "mcp-protocol-version": "2025-03-26",
      },
      json=payload,
      timeout=30,
  )

  response.raise_for_status()
  print(json.dumps(response.json(), indent=2))
  ```
</CodeGroup>

## Related tools

### Previous-step tools

* [`get_event_summary`](/sports-mcp-server/tool-reference/get_event_summary)

### Next-step tools

* [`get_event_center`](/sports-mcp-server/tool-reference/get_event_center)

### Alternative tools

* No common alternatives.

## Prompt patterns this tool fits

* Use `get_odds` when the host already knows the right scope and needs this job directly.

## Common mistakes

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