Skip to main content
Glama

flash-props-api

by io.github.iFan6oy
OverviewDiscussionsAdmin

Get player props for a specific game

get_game_props
Read-onlyIdempotent

Fetch all player props for one game identified by eventId. Read-only. No side effects. Requires an API key; rate-limited per your tier. Returns: { eventId, sport, homeTeam, awayTeam, startTime, props: Array<{ player, stat, line, overOdds, underOdds, bookCount, gameState?, flashProjection? }>, sources: string[], fetchedAt, delayed, snapshotId, snapshotConsistency }. flashProjection is present when that sport + market has a registered Flash model and a player baseline is available; it is { value, sampleN, method, marketKey, basis, seasonId, basisNote } and is never fabricated. basis prior_season means a prior-season baseline, never current form. overOdds and underOdds are American-format integers (e.g. -110, +115); null when odds are not available. The stats parameter filters to specific markets (e.g. "points,rebounds" for basketball, "strikeouts,hits_allowed" for MLB). Typical workflow: (1) call list_games to get eventIds, (2) call get_game_props with the eventId. Alternatively, call find_game with team names to resolve the eventId when you know the matchup. Event ids are prefixed ud- (Underdog Fantasy source). Returns an error when the event id is not found, the game has ended with no active props, or lines have not been posted yet. When to use: when you have an eventId and want all props for that specific game. When not to use: use scan_props instead when you want a cross-game market view. Use find_player_props when you know the player name but not which game they are in.

Input Schema

NameRequiredDescriptionDefault
sportNoSport id. Must match the sport the event belongs to. Omit to use the current in-season sport.
statsNoComma-separated list of stat keys to return, e.g. "points,rebounds,assists" for basketball or "strikeouts,hits_allowed" for MLB. Omit to return all available markets.
eventIdYesEvent id from list_games or find_game. Prefixed ud-, e.g. "ud-119284".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / eventId / description
      Previous value: -"Event id from list_games or find_game. Prefixed ud- or sc-, e.g. \"ud-119284\"."New value: +"Event id from list_games or find_game. Prefixed ud-, e.g. \"ud-119284\"."
  2. Changed1 schema field changed
    • changedInput schema / properties / eventId / description
      Previous value: -"Event id from list_games or find_game. Prefixed ud- or bv-, e.g. \"bv-26839935\" or \"ud-119284\"."New value: +"Event id from list_games or find_game. Prefixed ud- or sc-, e.g. \"ud-119284\"."
  3. Changed2 schema fields changed
    • changedInput schema / properties / sport / description
      Previous value: -"Sport id (nba, mlb, nfl, etc.). Must match the sport the event belongs to. Omit to use the current in-season sport."New value: +"Sport id. Must match the sport the event belongs to. Omit to use the current in-season sport."
    • changedInput schema / properties / stats / description
      Previous value: -"Comma-separated list of stat keys to return, e.g. \"points,rebounds,assists\" for NBA or \"strikeouts,hits_allowed\" for MLB. Omit to return all available markets."New value: +"Comma-separated list of stat keys to return, e.g. \"points,rebounds,assists\" for basketball or \"strikeouts,hits_allowed\" for MLB. Omit to return all available markets."
  4. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/no-destructive, and the description adds substantive context the annotations lack: API key requirement, tier-based rate limiting, and specific error conditions (unknown event id, ended game, unposted lines). It does not have to explain return format safety further given those error notes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Core purpose and workflow are front-loaded, and the return-structure detail is useful given no output schema. The description is long but nearly every sentence carries information; the extensive return-field breakdown could be slightly tightened.

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?

With no output schema, the description compensates by fully describing the return shape (eventId, props array, odds format, flashProjection fields, basis semantics) and the error conditions — an agent has everything needed to call and interpret the tool.

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 coverage is 100%, so all three parameters are already documented. The description restates the stats filtering with examples and mentions the ud- event id prefix, but adds little beyond what the schema itself says. 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?

States a specific verb and resource — 'Fetch all player props for one game identified by eventId' — and clearly separates itself from siblings scan_props and find_player_props later in the text.

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?

Provides an explicit numbered workflow (list_games -> get_game_props), an alternative resolution path via find_game, and a dedicated 'When to use / When not to use' block naming scan_props and find_player_props as the alternatives.

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

All flash-props-api 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