Lumify Sports Intelligence

get_odds

Read-onlyIdempotent

Get current betting odds for an event: per-bookmaker lines and last-updated time. Includes in-play quotes while the event is underway; books that have not quoted since kickoff are omitted. bookmaker defaults to pinnacle. Use 'all' or a comma-separated list for multiple books — still 1 credit. Default is main lines (is_main=true); set include_alts for alternate spread/total rungs. Final events include result (won/lost/push/void) graded from the pre-kickoff close. MLB, tennis, and soccer (MLS + big-five) mains also include fair_price and consensus mirrored from published assessments. Returns available:false with no charge if odds aren't posted for this event yet. If bookmaker is omitted and Pinnacle hasn't posted a line yet (common for the first/last games of a preseason slate), falls back to the best-covered other book and adds requested_bookmaker='pinnacle' plus fallback_bookmaker to the response instead of reporting no odds; an explicit bookmaker='pinnacle' never falls back. Use get_odds_history for line movement over time.

Input Schema

TableJSON Schema

Name	Required	Description
`event_id`	Yes	Event id, from list_events, query_events, or search results.
`bookmaker`	No	Bookmaker slug. Defaults to pinnacle. Valid: pinnacle, fanduel, draftkings, betmgm, caesars, bet365, circa, westgate, wynn, south_point, stations, hardrock, betonline, betr, betrivers, lowvig, bovada, all, or a comma-separated list.
`include_alts`	No	Include alternate spread/total rungs. Default false (mains only).

Output Schema

TableJSON Schema

Name	Required	Description
`event_id`	No
`available`	No
`bookmakers`	No	Per-book markets. Outcomes include is_main. In-play omits books that have not quoted since kickoff. Final events add result (won/lost/push/void) and close on the pre-kickoff point.
`last_updated`	No
`fallback_bookmaker`	No	The book actually returned when requested_bookmaker is present.
`requested_bookmaker`	No	Present only when the default (no bookmaker arg) request fell back to a different book because Pinnacle has no line yet — always 'pinnacle' when present.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 10, 2026

addedInput schema / properties / bookmaker / description

Added value: +"Bookmaker slug. Defaults to pinnacle. Valid: pinnacle, fanduel, draftkings, betmgm, caesars, bet365, circa, westgate, wynn, south_point, stations, hardrock, betonline, betr, betrivers, lowvig, bovada, all, or a comma-separated list."

addedInput schema / properties / event_id / description

Added value: +"Event id, from list_events, query_events, or search results."

addedInput schema / properties / include_alts

Added value: +{
+  "description": "Include alternate spread/total rungs. Default false (mains only).",
+  "type": "boolean"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "available": {
+      "type": "boolean"
+    },
+    "bookmakers": {
+      "description": "Per-book markets. Outcomes include is_main. In-play omits books that have not quoted since kickoff. Final events add result (won/lost/push/void) and close on the pre-kickoff point.",
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "event_id": {
+      "type": "integer"
+    },
+    "fallback_bookmaker": {
+      "description": "The book actually returned when requested_bookmaker is present.",
+      "type": "string"
+    },
+    "last_updated": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "requested_bookmaker": {
+      "description": "Present only when the default (no bookmaker arg) request fell back to a different book because Pinnacle has no line yet — always 'pinnacle' when present.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed4 schema fields changedSep 10, 2026

removedInput schema / properties / bookmaker / description

Removed value: -"Bookmaker slug. Defaults to pinnacle. Valid: pinnacle, fanduel, draftkings, betmgm, caesars, bet365, circa, westgate, wynn, south_point, stations, hardrock, betonline, betr, betrivers, lowvig, bovada, all, or a comma-separated list."

removedInput schema / properties / event_id / description

Removed value: -"Event id, from list_events, query_events, or search results."

removedInput schema / properties / include_alts

Removed value: -{
-  "description": "Include alternate spread/total rungs. Default false (mains only).",
-  "type": "boolean"
-}

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "available": {
-      "type": "boolean"
-    },
-    "bookmakers": {
-      "description": "Per-book markets. Outcomes include is_main. In-play omits books that have not quoted since kickoff. Final events add result (won/lost/push/void) and close on the pre-kickoff point.",
-      "items": {
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "event_id": {
-      "type": "integer"
-    },
-    "fallback_bookmaker": {
-      "description": "The book actually returned when requested_bookmaker is present.",
-      "type": "string"
-    },
-    "last_updated": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "requested_bookmaker": {
-      "description": "Present only when the default (no bookmaker arg) request fell back to a different book because Pinnacle has no line yet — always 'pinnacle' when present.",
-      "type": "string"
-    }
-  },
-  "type": "object"
-}New value: +null

Changed1 schema field changedSep 6, 2026

changedInput schema / properties / bookmaker / description

Previous value: -"Bookmaker slug. Defaults to pinnacle. Valid: pinnacle, fanduel, draftkings, betmgm, caesars, bet365, circa, westgate, wynn, south_point, stations, hardrock, betonline, betr, betrivers, lowvig, all, or a comma-separated list."New value: +"Bookmaker slug. Defaults to pinnacle. Valid: pinnacle, fanduel, draftkings, betmgm, caesars, bet365, circa, westgate, wynn, south_point, stations, hardrock, betonline, betr, betrivers, lowvig, bovada, all, or a comma-separated list."

Changed1 schema field changedSep 3, 2026

changedInput schema / properties / bookmaker / description

Previous value: -"Bookmaker slug. Defaults to pinnacle. Valid: pinnacle, fanduel, draftkings, betmgm, caesars, bet365, circa, westgate, wynn, south_point, stations, hardrock, betonline, betr, betrivers, all, or a comma-separated list."New value: +"Bookmaker slug. Defaults to pinnacle. Valid: pinnacle, fanduel, draftkings, betmgm, caesars, bet365, circa, westgate, wynn, south_point, stations, hardrock, betonline, betr, betrivers, lowvig, all, or a comma-separated list."

Changed1 schema field changedSep 2, 2026

changedInput schema / properties / bookmaker / description

Previous value: -"Bookmaker slug. Defaults to pinnacle. Valid: pinnacle, fanduel, draftkings, betmgm, caesars, bet365, circa, hardrock, betonline, all, or a comma-separated list."New value: +"Bookmaker slug. Defaults to pinnacle. Valid: pinnacle, fanduel, draftkings, betmgm, caesars, bet365, circa, westgate, wynn, south_point, stations, hardrock, betonline, betr, betrivers, all, or a comma-separated list."

Changed1 schema field changedAug 24, 2026

changedOutput schema / properties / bookmakers / description

Previous value: -"Per-book markets. Outcomes include is_main; final events add result (won/lost/push/void) and close on graded points."New value: +"Per-book markets. Outcomes include is_main. In-play omits books that have not quoted since kickoff. Final events add result (won/lost/push/void) and close on the pre-kickoff point."

Changed2 schema fields changedAug 22, 2026

addedOutput schema / properties / fallback_bookmaker

Added value: +{
+  "description": "The book actually returned when requested_bookmaker is present.",
+  "type": "string"
+}

addedOutput schema / properties / requested_bookmaker

Added value: +{
+  "description": "Present only when the default (no bookmaker arg) request fell back to a different book because Pinnacle has no line yet — always 'pinnacle' when present.",
+  "type": "string"
+}

Changed2 schema fields changedAug 20, 2026

addedInput schema / properties / include_alts

Added value: +{
+  "description": "Include alternate spread/total rungs. Default false (mains only).",
+  "type": "boolean"
+}

addedOutput schema / properties / bookmakers / description

Added value: +"Per-book markets. Outcomes include is_main; final events add result (won/lost/push/void) and close on graded points."

Changed1 schema field changedJul 24, 2026

changedInput schema / properties / bookmaker / description

Previous value: -"Bookmaker slug, e.g. pinnacle (default) or 'all' for every book."New value: +"Bookmaker slug. Defaults to pinnacle. Valid: pinnacle, fanduel, draftkings, betmgm, caesars, bet365, circa, hardrock, betonline, all, or a comma-separated list."

Changed1 schema field changedJul 21, 2026
- changedOutput schema / properties / last_updated / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```

Changed3 schema fields changedJul 20, 2026

addedInput schema / properties / bookmaker / description

Added value: +"Bookmaker slug, e.g. pinnacle (default) or 'all' for every book."

addedInput schema / properties / event_id / description

Added value: +"Event id, from list_events, query_events, or search results."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "available": {
+      "type": "boolean"
+    },
+    "bookmakers": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "event_id": {
+      "type": "integer"
+    },
+    "last_updated": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedJul 12, 2026

TDQS

A5/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already mark this read-only and idempotent, but the description adds substantial behavioral detail beyond that: no-charge available:false responses, fallback to another bookmaker, credit cost for multiple books, omission of books that have not quoted since kickoff, and result grading from pre-kickoff close. This is far more than the annotations alone provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense but front-loaded with the core purpose, and every sentence adds useful operational or behavioral context. No filler is present, and the detail about fallback, credits, and alternatives earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity and the existence of an output schema, the description is complete enough for correct invocation. It covers defaults, edge cases (unposted odds, preseason slates), in-play behavior, final-event results, and related tools, leaving no critical ambiguity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description goes well beyond the schema: it explains 'all' and comma-separated lists cost 1 credit, clarifies the default main-lines behavior, and documents the fallback semantics when bookmaker is omitted. This adds meaning that the schema does not convey.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Get current betting odds for an event: per-bookmaker lines and last-updated time.' It clearly defines the tool's scope and distinguishes it from get_odds_history by directing line-movement queries to that sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides explicit usage context: defaults, multi-book selection, in-play behavior, final-event result grading, and a clear alternative ('Use get_odds_history for line movement over time'). It also explains fallback behavior when Pinnacle has no posted line, which helps the agent decide when this tool is appropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Lumify Sports Intelligence tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

get_odds

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources