Skip to main content
Glama

Lumify Sports Intelligence

get_event

Read-onlyIdempotent

Get a single event with participants and venue. Optionally inline current odds and/or bet intelligence (same 1 credit as the event call). Raises a not-found error if event_id doesn't exist. Use list_events / query_events to discover ids first, or batch_get_events to fetch several ids in one call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
event_idYesEvent id, from list_events, query_events, or search results.
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.
include_oddsNoInline current odds scoped by bookmaker (default: pinnacle). Does not add credits — the event call stays 1 credit.
include_intelligenceNoInline bet intelligence. Does not add credits.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
nameNo
sportNo
venueNo
leagueNo
statusNo
starts_atNo
updated_atNo
participantsNo
inprogress_sinceNoISO-8601 UTC when status first became inprogress (first live tick). Null until then; stays set after final.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 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, westgate, wynn, south_point, stations, hardrock, betonline, betr, betrivers, lowvig, bovada, all."
    • addedInput schema / properties / event_id / description
      Added value: +"Event id, from list_events, query_events, or search results."
    • changedInput schema / properties / include_intelligence / description
      Previous value: -"Inline bet intelligence (+1 credit when available)."New value: +"Inline bet intelligence. Does not add credits."
    • changedInput schema / properties / include_odds / description
      Previous value: -"Inline current odds (+1 credit when odds are available)."New value: +"Inline current odds scoped by bookmaker (default: pinnacle). Does not add credits — the event call stays 1 credit."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "id": {
      +      "type": "integer"
      +    },
      +    "inprogress_since": {
      +      "description": "ISO-8601 UTC when status first became inprogress (first live tick). Null until then; stays set after final.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "league": {
      +      "type": "string"
      +    },
      +    "name": {
      +      "type": "string"
      +    },
      +    "participants": {
      +      "items": {
      +        "properties": {
      +          "is_winner": {
      +            "type": [
      +              "boolean",
      +              "null"
      +            ]
      +          },
      +          "participant_id": {
      +            "type": "integer"
      +          },
      +          "player": {
      +            "type": [
      +              "object",
      +              "null"
      +            ]
      +          },
      +          "role": {
      +            "type": "string"
      +          },
      +          "score": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "team": {
      +            "type": [
      +              "object",
      +              "null"
      +            ]
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "sport": {
      +      "type": "string"
      +    },
      +    "starts_at": {
      +      "type": "string"
      +    },
      +    "status": {
      +      "type": "string"
      +    },
      +    "updated_at": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "venue": {
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    }
      +  },
      +  "type": "object"
      +}
  2. Changed5 schema fields 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, bovada, all."New value: +"Bookmaker for inlined odds; defaults to pinnacle, 'all' for every book."
    • removedInput schema / properties / event_id / description
      Removed value: -"Event id, from list_events, query_events, or search results."
    • changedInput schema / properties / include_intelligence / description
      Previous value: -"Inline bet intelligence. Does not add credits."New value: +"Inline bet intelligence (+1 credit when available)."
    • changedInput schema / properties / include_odds / description
      Previous value: -"Inline current odds scoped by bookmaker (default: pinnacle). Does not add credits — the event call stays 1 credit."New value: +"Inline current odds (+1 credit when odds are available)."
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "id": {
      -      "type": "integer"
      -    },
      -    "inprogress_since": {
      -      "description": "ISO-8601 UTC when status first became inprogress (first live tick). Null until then; stays set after final.",
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "league": {
      -      "type": "string"
      -    },
      -    "name": {
      -      "type": "string"
      -    },
      -    "participants": {
      -      "items": {
      -        "properties": {
      -          "is_winner": {
      -            "type": [
      -              "boolean",
      -              "null"
      -            ]
      -          },
      -          "participant_id": {
      -            "type": "integer"
      -          },
      -          "player": {
      -            "type": [
      -              "object",
      -              "null"
      -            ]
      -          },
      -          "role": {
      -            "type": "string"
      -          },
      -          "score": {
      -            "type": [
      -              "string",
      -              "null"
      -            ]
      -          },
      -          "team": {
      -            "type": [
      -              "object",
      -              "null"
      -            ]
      -          }
      -        },
      -        "type": "object"
      -      },
      -      "type": "array"
      -    },
      -    "sport": {
      -      "type": "string"
      -    },
      -    "starts_at": {
      -      "type": "string"
      -    },
      -    "status": {
      -      "type": "string"
      -    },
      -    "updated_at": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "venue": {
      -      "type": [
      -        "object",
      -        "null"
      -      ]
      -    }
      -  },
      -  "type": "object"
      -}New value: +null
  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
    • addedOutput schema / properties / inprogress_since
      Added value: +{
      +  "description": "ISO-8601 UTC when status first became inprogress (first live tick). Null until then; stays set after final.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  6. 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."
  7. Changed2 schema fields changed
    • changedInput schema / properties / include_intelligence / description
      Previous value: -"Inline bet intelligence (+1 credit when available)."New value: +"Inline bet intelligence. Does not add credits."
    • changedInput schema / properties / include_odds / description
      Previous value: -"Inline current odds scoped by bookmaker (default: pinnacle). +1 credit 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 — the event call stays 1 credit."
  8. 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 (+1 credit when odds are available)."New value: +"Inline current odds scoped by bookmaker (default: pinnacle). +1 credit for a single book when available; +2 for bookmaker=all or a comma-separated list."
  9. Changed6 schema fields changed
    • changedOutput schema / properties / participants / items / properties / is_winner / type
      Previous value: -"boolean"New value: +[
      +  "boolean",
      +  "null"
      +]
    • changedOutput schema / properties / participants / items / properties / player / type
      Previous value: -"object"New value: +[
      +  "object",
      +  "null"
      +]
    • changedOutput schema / properties / participants / items / properties / score / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / participants / items / properties / team / type
      Previous value: -"object"New value: +[
      +  "object",
      +  "null"
      +]
    • changedOutput schema / properties / updated_at / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / venue / type
      Previous value: -"object"New value: +[
      +  "object",
      +  "null"
      +]
  10. Changed2 schema fields changed
    • 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": {
      +    "id": {
      +      "type": "integer"
      +    },
      +    "league": {
      +      "type": "string"
      +    },
      +    "name": {
      +      "type": "string"
      +    },
      +    "participants": {
      +      "items": {
      +        "properties": {
      +          "is_winner": {
      +            "type": "boolean"
      +          },
      +          "participant_id": {
      +            "type": "integer"
      +          },
      +          "player": {
      +            "type": "object"
      +          },
      +          "role": {
      +            "type": "string"
      +          },
      +          "score": {
      +            "type": "string"
      +          },
      +          "team": {
      +            "type": "object"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "sport": {
      +      "type": "string"
      +    },
      +    "starts_at": {
      +      "type": "string"
      +    },
      +    "status": {
      +      "type": "string"
      +    },
      +    "updated_at": {
      +      "type": "string"
      +    },
      +    "venue": {
      +      "type": "object"
      +    }
      +  },
      +  "type": "object"
      +}
  11. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds valuable context beyond annotations: it states that a not-found error is raised for invalid ids and that inlining odds/intelligence does not add credits. This enriches the behavioral profile without contradicting the annotations.

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 no filler. It front-loads the core purpose, then covers alternatives and error behavior efficiently. Every sentence 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 has an output schema, the description need not explain return values. It covers discovery, batching, error handling, and credit semantics. Nothing an agent needs to correctly invoke it is missing.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds meaningful extra semantics by noting that include_odds and include_intelligence do not increase the credit cost, which is not present in the schema. This justifies a score above baseline.

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 clearly states the verb 'Get' and the resource 'a single event with participants and venue', which is specific and distinguishes it from batch_get_events, list_events, and query_events. It also mentions optional inlining of odds and intelligence, further clarifying scope.

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?

Explicitly directs the agent to use list_events/query_events to discover ids first, or batch_get_events for multiple ids. It also clarifies when to use this tool versus alternatives, which is exactly what usage guidelines require.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.