Skip to main content
Glama

Lumify Sports Intelligence

by ai.lumify
OverviewDiscussionsAdmin

get_player_props

Read-onlyIdempotent

Get player-prop lines and live progress for an NFL, NCAAF, NBA, NCAAB, NHL, MLB, or soccer event. Joins persisted player-prop mains to this-event player box counts and grades over/under/push (1:1 slugs, combo sums including rush+rec and pass+rush yards, weighted total bases, anytime TD, double-double/triple-double, hockey points). Sport × market catalog: https://lumify.ai/docs/player-props. GET /odds / get_odds stay on moneyline/spread/total. Returns available:false with no charge if no prop mains have been ingested. Other sports return HTTP 400.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
event_idYesEvent id, from list_events, query_events, or search results.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
clockNoGame clock from the live score snapshot.
sportNoSport slug: nfl, ncaaf, nba, ncaab, nhl, or mlb.
periodNoCurrent period from the live score snapshot.
statusNoEvent status (scheduled, inprogress, delayed, final, …).
event_idNoLumify event ID.
availableNoFalse when no player-prop mains have been ingested; player_props is empty and the call isn't billed.
player_propsNoOne row per (player, market, line). Fields: player, player_id (null if unmatched), market (prop category), line, current (this-event box count), pct_of_line, settleable, result (in_progress / over / under / push / dnp — box landed and this player has zero rows / no_stat — played but this slug never landed, unmatched, or box not landed yet; null when not settleable), books ({book_slug: {over, under}} American prices).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Changed1 schema field changed
    • changedOutput schema / properties / player_props / description
      Previous value: -"One row per (player, market, line). Fields: player, player_id (null if unmatched), market (prop category), line, current (this-event box count), pct_of_line, settleable, result (in_progress / over / under / push, or null), books ({book_slug: {over, under}} American prices)."New value: +"One row per (player, market, line). Fields: player, player_id (null if unmatched), market (prop category), line, current (this-event box count), pct_of_line, settleable, result (in_progress / over / under / push / dnp — box landed and this player has zero rows / no_stat — played but this slug never landed, unmatched, or box not landed yet; null when not settleable), books ({book_slug: {over, under}} American prices)."
  4. Changed1 schema field changed
    • changedOutput schema / properties / sport / description
      Previous value: -"Sport slug: nfl, ncaaf, nba, ncaab, or nhl."New value: +"Sport slug: nfl, ncaaf, nba, ncaab, nhl, or mlb."
  5. Changed1 schema field changed
    • changedOutput schema / properties / sport / description
      Previous value: -"Sport slug: nfl, ncaaf, nba, or ncaab."New value: +"Sport slug: nfl, ncaaf, nba, ncaab, or nhl."
  6. Changed1 schema field changed
    • changedOutput schema / properties / sport / description
      Previous value: -"Sport slug: nfl, ncaaf, or nba."New value: +"Sport slug: nfl, ncaaf, nba, or ncaab."
  7. Changed1 schema field changed
    • changedOutput schema / properties / sport / description
      Previous value: -"Sport slug: nfl or nba."New value: +"Sport slug: nfl, ncaaf, or nba."
  8. Changed1 schema field changed
    • changedOutput schema / properties / player_props / description
      Previous value: -"One row per (player, market, line). Fields: player, player_id (null if unmatched), market (Owls category), line, current (this-event box count), pct_of_line, settleable, result (in_progress / over / under / push, or null), books ({book_slug: {over, under}} American prices)."New value: +"One row per (player, market, line). Fields: player, player_id (null if unmatched), market (prop category), line, current (this-event box count), pct_of_line, settleable, result (in_progress / over / under / push, or null), books ({book_slug: {over, under}} American prices)."
  9. Added

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnly/openWorld/idempotent annotations, the description discloses no-charge behavior, available:false semantics, HTTP 400 for unsupported sports, and the joined/grading logic. These are concrete behavioral traits not inferable from annotations alone.

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?

First sentence front-loads purpose, and each subsequent sentence earns its place: market catalog, sibling distinction, no-charge condition, and error behavior. No waste or repetition.

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?

Description covers what the tool returns, which sports are supported, behavior when data is absent, HTTP error cases, and where to find the full catalog. Since an output schema and annotations exist, the description does not need to explain return values or safety traits.

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?

The single parameter event_id is fully documented in the schema, so baseline is 3. The description adds sport restrictions and error behavior for invalid event types, adding meaning beyond the schema's generic 'from list_events' source.

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 opens with a specific verb and object: 'Get player-prop lines and live progress' for a defined set of sports. It clearly scopes the resource and differentiates itself from get_odds by stating that odds endpoints stay on moneyline/spread/total.

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 tells an agent to use get_odds for non-player-prop markets, and states when the tool returns available:false or HTTP 400. This gives clear conditions for selecting this tool versus alternatives.

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