Skip to main content
Glama

Lumify Sports Intelligence

by ai.lumify

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
NameRequiredDescriptionDefault
event_idYesEvent id, from list_events, query_events, or search results.
bookmakerNoBookmaker 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.
include_altsNoInclude alternate spread/total rungs. Default false (mains only).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
event_idNo
availableNo
bookmakersNoPer-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_updatedNo
fallback_bookmakerNoThe book actually returned when requested_bookmaker is present.
requested_bookmakerNoPresent 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. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • 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."
  2. Changed1 schema field changed
    • 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."
  3. Changed1 schema field changed
    • 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."
  4. Changed2 schema fields changed
    • 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"
+}
  5. Changed2 schema fields changed
    • 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."
  6. Changed1 schema field changed
    • 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."
  7. Changed1 schema field changed
    • changedOutput schema / properties / last_updated / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
  8. Changed3 schema fields changed
    • 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"
+}
  9. First observed

TDQS

A5/5.0
Behavior5/5

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

Annotations already mark this as read-only, open-world, idempotent, and non-destructive. The description adds substantial behavioral context beyond that: books with no recent quote are omitted, unavailable events return available:false with no charge, fallback bookmaker behavior is explained, and the result grading from pre-kickoff close is disclosed. No contradiction exists.

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?

Every sentence in the description carries operational information an agent needs: defaults, fallbacks, charge behavior, availability semantics, and sibling routing. Though the paragraph is dense, it is appropriately sized for the tool's complexity and front-loads the core purpose before edge cases.

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 presence of an output schema, the description covers all critical contextual gaps: live-event behavior, missing-odds handling, fallback selection rules, alternate markets, result grading, and fair_price availability. An agent selecting or invoking this tool has enough information to predict behavior across edge cases.

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 already strong. The description goes much further by explaining default values ('bookmaker defaults to pinnacle'), the special 'all' and comma-separated syntax, the 1-credit guarantee across multiple books, and the interaction between include_alts and main lines. This adds meaning well beyond the raw parameter descriptions.

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,' followed by the key outputs (per-bookmaker lines, last-updated time). It clearly differentiates from the sibling get_odds_history by explicitly routing line-movement queries there.

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?

The description gives explicit when-to-use guidance, including behaviors for live events, post-event grading, unavailable odds, and fallback selection. It names get_odds_history as the alternative for line movement over time, making the choice between siblings unambiguous.

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 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool maps to a distinct data resource or operation: events, live scores, odds, odds history, splits, stats, intelligence, player props, players, teams, sports, and seasons. Pairs like list_events vs query_events and get_event vs get_live_score are clearly differentiated by structured vs natural-language filtering and lightweight vs full detail.

Naming Consistency5/5

Tool names consistently follow a verb_noun snake_case pattern: get_*, list_*, search_*, query_*, batch_get_*, and estimate_cost. The naming conventions make the resource family immediately obvious, and deviations like batch_get_events are still predictable variants.

Tool Count4/5

19 tools is on the higher side, but each tool covers a specific sports-intelligence data product or workflow with little redundancy. The count feels intentional for the breadth of the domain rather than bloated.

Completeness4/5

The surface covers event discovery and retrieval, live scores, odds and line movement, splits, statistics, player props, intelligence, player/team/sport/season lookups, batch fetching, and cost estimation. Minor gaps like team standings or full rosters are not exposed, but core agent workflows are well supported.

Resources