Skip to main content
Glama

Lumify Sports Intelligence

by ai.lumify

batch_get_events

Read-onlyIdempotent

Get multiple events by id in one call — for agents that already have a list of ids and want full detail for each without one call per event. Max 25 ids. Returns full detail for every id that exists plus a not_found list for any that don't (never billed). Use get_event for a single id, or list_events / query_events to discover ids first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bookmakerNoBookmaker for inlined odds and intelligence market prices. Defaults to pinnacle. Valid: pinnacle, fanduel, draftkings, betmgm, caesars, bet365, circa, westgate, wynn, south_point, stations, hardrock, betonline, betr, betrivers, lowvig, all.
event_idsYesEvent ids to fetch (max 25); duplicates are billed once.
include_oddsNoInline current odds scoped by bookmaker (default: pinnacle). Does not add credits — each found event stays 1 credit.
include_intelligenceNoInline bet intelligence on each event. Does not add credits.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
totalNo
eventsNoFull event detail (same shape as get_event) for every found id.
not_foundNoRequested event_ids that don't exist. Never billed.

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 for inlined odds and intelligence market prices. Defaults to pinnacle. Valid: pinnacle, fanduel, draftkings, betmgm, caesars, bet365, circa, westgate, wynn, south_point, stations, hardrock, betonline, betr, betrivers, all."New value: +"Bookmaker for inlined odds and intelligence market prices. Defaults to pinnacle. Valid: pinnacle, fanduel, draftkings, betmgm, caesars, bet365, circa, westgate, wynn, south_point, stations, hardrock, betonline, betr, betrivers, lowvig, all."
  2. Changed1 schema field changed
    • changedInput schema / properties / bookmaker / description
      Previous value: -"Bookmaker for inlined odds and intelligence market prices. Defaults to pinnacle. Valid: pinnacle, fanduel, draftkings, betmgm, caesars, bet365, circa, hardrock, betonline, all."New value: +"Bookmaker for inlined odds and intelligence market prices. Defaults to pinnacle. Valid: pinnacle, fanduel, draftkings, betmgm, caesars, bet365, circa, westgate, wynn, south_point, stations, hardrock, betonline, betr, betrivers, all."
  3. Changed2 schema fields changed
    • changedInput schema / properties / include_intelligence / description
      Previous value: -"Inline bet intelligence on each event (+1 credit per event when available)."New value: +"Inline bet intelligence on each event. Does not add credits."
    • changedInput schema / properties / include_odds / description
      Previous value: -"Inline current odds scoped by bookmaker (default: pinnacle). +1 credit per event for a single book when available; +2 for bookmaker=all or a comma-separated list."New value: +"Inline current odds scoped by bookmaker (default: pinnacle). Does not add credits — each found event stays 1 credit."
  4. Changed2 schema fields changed
    • changedInput schema / properties / bookmaker / description
      Previous value: -"Bookmaker for inlined odds; defaults to pinnacle, 'all' for every book."New value: +"Bookmaker for inlined odds and intelligence market prices. Defaults to pinnacle. Valid: pinnacle, fanduel, draftkings, betmgm, caesars, bet365, circa, hardrock, betonline, all."
    • changedInput schema / properties / include_odds / description
      Previous value: -"Inline current odds on each event (+1 credit per event when odds are available)."New value: +"Inline current odds scoped by bookmaker (default: pinnacle). +1 credit per event for a single book when available; +2 for bookmaker=all or a comma-separated list."
  5. Changed2 schema fields changed
    • changedInput schema / properties / event_ids / description
      Previous value: -"Event ids to fetch."New value: +"Event ids to fetch (max 25); duplicates are billed once."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "events": {
+      "description": "Full event detail (same shape as get_event) for every found id.",
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "not_found": {
+      "description": "Requested event_ids that don't exist. Never billed.",
+      "items": {
+        "type": "integer"
+      },
+      "type": "array"
+    },
+    "total": {
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}
  6. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already mark this read-only, idempotent, and non-destructive. The description adds valuable behavioral detail beyond that: a 25-id max, full detail for existing ids plus a not_found list, and that missing ids are never billed. This extra operational context helps an agent predict side effects and cost.

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?

Three dense sentences carry the primary purpose, constraints, billing behavior, output shape, and sibling routing. Every sentence earns its place, and the most decision-relevant information is front-loaded.

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 batch-read tool with a rich output schema and annotations, the description covers everything needed to invoke it correctly: when to use it, max batch size, return behavior, and which sibling to use instead. No critical 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?

Schema description coverage is 100%, so the schema fully documents event_ids, bookmaker, include_odds, and include_intelligence. The description adds the high-level batching/billing behavior but no per-parameter details beyond what the schema already provides, so the baseline 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?

Description leads with a specific verb-resource pair ('Get multiple events by id in one call') and clearly distinguishes the batch operation from its single-id sibling get_event. It names the intended use case (agents that already have ids and want full detail) without ambiguity.

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 explicitly states when to use this tool: when the agent already has a list of ids and wants full detail without per-event calls. It also names alternatives and the routing condition: use get_event for a single id, or list_events / query_events to discover ids first.

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