Skip to main content
Glama
odds-api-io

Odds-API MCP Server

Official
by odds-api-io

get_dropping_odds

Identifies odds with the largest drops from opening using sharp bookmaker data, updated every 10 seconds, to track sharp money movement across multiple time windows.

Instructions

Get odds that have dropped the most from opening, based on sharp bookmaker data. Useful for tracking where sharp money is moving. Updated every ~10 seconds. Only available on paid plans. Response includes drop percentages for multiple time windows (sinceOpening, 12h, 24h, 48h). For player prop markets, the response includes market.label with the player name (e.g. 'Carlos Baleba'). Use markets=Player Props to get all player prop markets across all sports (football includes Anytime Goalscorer, Player Passes, Player Shots, Player Shots on Target, etc.). IMPORTANT: Always pass the sport parameter when the user mentions or implies a specific sport — the global (no-sport) endpoint is heavily dominated by player props and will return very few main market results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sportNoSport slug to filter by (e.g., 'football', 'basketball'). Always include this when the user mentions a sport — without it, results are dominated by player props and main market drops are hidden.
leagueNoSingle league slug to filter by (e.g., 'england-premier-league'). Requires sport. Mutually exclusive with leagues.
leaguesNoComma-separated league slugs to filter by multiple leagues (e.g., 'england-premier-league,spain-la-liga'). Mutually exclusive with league. When used with sport, fetches full per-league data instead of the pre-truncated global snapshot.
marketsNoComma-separated market names to filter by (case-insensitive). e.g. 'ML,Spread,Totals'. Supported: ML, Spread, Totals, Spread HT, Totals HT, Totals 1Q, Spread 1Q, Team Total Home, Team Total Away, Corners Spread, Corners Totals, Corners Spread HT, Corners Totals HT, Bookings Spread, Bookings Totals, Player Props. Note: 'Player Props' returns all player prop markets across all sports.
timeWindowNoTime window for drop filtering and sorting: 'opening', '12h', '24h', '48h' (default: 'opening')
sortNoSort order: 'drop' (highest drop %), 'recent' (latest movement), 'kickoff' (soonest event). Default: 'drop'
minDropNoMinimum drop percentage threshold (default: 0)
limitNoResults per page, 1-200 (default: 50)
pageNoPage number, 1-indexed (default: 1)
includeEventDetailsNoInclude expanded event details (home, away, date, sport, league) in response
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses update frequency (~10 sec), paid plan requirement, response structure (multiple time windows, player prop labeling), and the dominance of player props without sport parameter. This is solid transparency.

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?

The description is reasonably concise, with front-loaded purpose. Each sentence adds value, though it could be slightly more terse. Structure is logical: purpose, update frequency, availability, response hints, then usage tips.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 10 parameters and no output schema, the description covers key behavioral aspects (update, paid, player props) and parameter usage (sport importance). It misses some details like pagination behavior but is largely complete for an agent to use correctly.

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 baseline is 3. The description adds context about sport parameter importance and player props but does not significantly enhance understanding beyond the schema's parameter descriptions.

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 tool retrieves odds that have dropped most from opening using sharp bookmaker data. It distinguishes from sibling tools like get_odds and get_odds_movements by focusing on drops and sharp data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit guidance: always include the sport parameter when a sport is implied, and notes the tool is only on paid plans. It does not explicitly state when not to use or compare to alternatives, but the guidance is helpful.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/odds-api-io/odds-api-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server