Skip to main content
Glama

Lumify Sports Intelligence

by ai.lumify
OverviewDiscussionsAdmin

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, bovada, 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.

  1. Added
  2. Removed
  3. 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, lowvig, 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, bovada, all."
  4. 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."
  5. 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."
  6. 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."
  7. 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."
  8. 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"
+}
  9. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context beyond annotations: the max 25 id limit, the not_found list for missing ids, that not_found entries are never billed, and that include_odds/include_intelligence do not add credits. It also clarifies that duplicates are billed once, which is crucial for cost-sensitive agents.

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 two sentences with zero wasted words. The primary purpose is front-loaded, followed by the max limit, return behavior, billing nuance, and sibling alternatives. Every clause adds value, and the structure guides the agent from action to 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 that an output schema exists, the description doesn't need to enumerate return fields. It covers the critical contextual points: id list requirement, max 25, not_found behavior, billing implications, and when to use siblings. The description fully equips an agent to decide and call correctly without missing prerequisites or caveats.

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 every parameter is already documented in the input schema. The description does not add new parameter-specific meaning beyond what the schema provides; it restates the max 25 limit and duplicates-billed-once, which are also in the schema. Baseline of 3 applies because the schema fully covers parameter semantics.

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 precise verb+resource ('Get multiple events by id in one call') and immediately distinguishes it from sibling tools by stating it's for agents that already have ids and want full detail without one call per event. It also names the sibling alternatives (get_event, list_events, query_events) and explains the distinction.

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 ('for agents that already have a list of ids') and when not to, naming the alternatives: 'Use get_event for a single id, or list_events / query_events to discover ids first.' This is clear guidance with no ambiguity.

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

Resources