Flash Props API
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FLASH_PROPS_API_KEY | No | API key for authenticating requests. Get a free key at https://api.flashodds.live/connect |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_sportsA | List supported sports and whether your API key tier can access each. |
| list_gamesA | List today's games with player props for a sport (nba, mlb, nfl, nhl, ncaab, ncaaf, soccer). Live games first. |
| get_game_propsA | Get player props for one game by event id (from list_games; ids are prefixed ud- or bv-). |
| scan_propsA | Market-wide scan: all player props across today's games for a sport, flattened into rows. Optionally filter by a single stat. |
| find_gameA | Resolve a matchup description (home and away team names) to an event id you can pass to get_game_props. Use this when you know the teams but not the event id. Returns { eventId } on success, or an error if no matching game is found for today's slate. Team names are matched case-insensitively and support partial names (e.g. "Yankees", "New York Yankees", "NYY" all work for MLB). If no game is found, the matchup may not be on today's board or the sport may be out of season. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: resolving team names to event IDs, retrieving props for a specific game, listing games for a sport, listing supported sports, and scanning all props across games. There is no overlap.
All tool names follow a consistent verb_noun pattern using lowercase with underscores: find_game, get_game_props, list_games, list_sports, scan_props. This pattern is uniform and predictable.
With 5 tools covering the essential operations for a sports props API (listing sports, listing games, resolving matchups, retrieving individual game props, and scanning all props), the count is well-scoped and each tool earns its place.
The tool set covers the full lifecycle of accessing player props: discovering available sports, listing games, resolving matchups, retrieving props for a specific game, and performing a market-wide scan. No obvious gaps are present for a read-only API.