Lumify Sports Intelligence

get_splits

Read-onlyIdempotent

Get public betting splits (bets% and handle%) for an event: a consensus split plus a per-bookmaker breakdown (bookmakers[].bookmaker uses the same odds slugs as get_odds, e.g. draftkings — not upstream short keys like dk), with a captured_at timestamp. Available for MLB, NBA, NHL, NFL, NCAAF, and NCAAB. Not available for tennis or soccer (upstream 400). Returns available:false with no charge if splits haven't been captured for this event yet or the sport is unsupported.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "event_id": "<event_id>"
    },
    "name": "get_splits"
  }
}

Input Schema

Name	Required	Description	Default
`event_id`	Yes	Event id, from list_events, query_events, or search results.

Output Schema

Name	Required	Description
`event_id`	No
`available`	No
`consensus`	No	Aggregate bets%/handle% across bookmakers.
`bookmakers`	No	Per-bookmaker splits. Each item has bookmaker (odds slug), name, moneyline, spread, total.
`captured_at`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 10, 2026

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": {
+      "description": "Per-bookmaker splits. Each item has bookmaker (odds slug), name, moneyline, spread, total.",
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "captured_at": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "consensus": {
+      "description": "Aggregate bets%/handle% across bookmakers.",
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "event_id": {
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

Changed2 schema fields changedSep 10, 2026

removedInput schema / properties / event_id / description

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

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "available": {
-      "type": "boolean"
-    },
-    "bookmakers": {
-      "description": "Per-bookmaker splits. Each item has bookmaker (odds slug), name, moneyline, spread, total.",
-      "items": {
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "captured_at": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "consensus": {
-      "description": "Aggregate bets%/handle% across bookmakers.",
-      "type": [
-        "object",
-        "null"
-      ]
-    },
-    "event_id": {
-      "type": "integer"
-    }
-  },
-  "type": "object"
-}New value: +null

Changed3 schema fields changedAug 10, 2026

addedOutput schema / properties / bookmakers

Added value: +{
+  "description": "Per-bookmaker splits. Each item has bookmaker (odds slug), name, moneyline, spread, total.",
+  "items": {
+    "type": "object"
+  },
+  "type": "array"
+}

removedOutput schema / properties / books

Removed value: -{
-  "description": "Per-bookmaker splits breakdown.",
-  "items": {
-    "type": "object"
-  },
-  "type": "array"
-}

changedOutput schema / properties / consensus / description

Previous value: -"Aggregate bets%/handle% across books."New value: +"Aggregate bets%/handle% across bookmakers."

Changed2 schema fields changedJul 21, 2026
- changedOutput schema / properties / captured_at / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / consensus / type
```
Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
```

Changed2 schema fields changedJul 20, 2026

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"
+    },
+    "books": {
+      "description": "Per-bookmaker splits breakdown.",
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "captured_at": {
+      "type": "string"
+    },
+    "consensus": {
+      "description": "Aggregate bets%/handle% across books.",
+      "type": "object"
+    },
+    "event_id": {
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

First observedJul 12, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already cover readOnly, openWorld, idempotent, and non-destructive behavior. The description adds valuable detail beyond that: no charge when splits are unavailable, upstream 400 errors for unsupported sports, and the bookmaker slug mapping convention relative to get_odds.

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

Conciseness4/5

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

The description is dense and front-loaded with the core purpose, followed by availability and fallback behavior. The first sentence is long with parentheticals, but every part earns its place; it could be slightly restructured for readability without losing content.

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?

For a one-parameter read-only tool with an output schema, the description is complete: it states what is returned, which sports are supported, when no data is available, and the billing behavior. No critical calling context is missing.

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

Parameters3/5

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

The schema fully covers the only required parameter, event_id, with guidance to source it from list_events, query_events, or search results. The description does not add extra parameter-level meaning beyond what the schema already provides, so the baseline of 3 applies.

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 begins with a specific verb and resource: 'Get public betting splits (bets% and handle%) for an event'. It clearly distinguishes the tool from siblings like get_odds by describing the exact data returned: consensus split, per-bookmaker breakdown, and captured_at timestamp.

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

Usage Guidelines4/5

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

The description provides clear usage context by listing supported sports (MLB, NBA, NHL, NFL, NCAAF, NCAAB) and explicitly stating tennis and soccer are not available. It also explains when the tool returns available:false, but it does not name an alternative tool or explicitly say when to prefer get_splits over get_odds.

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_splits

Tool call template

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources