Skip to main content
Glama

Market odds

get_market_odds
Read-onlyIdempotent

Use for the extra betting markets of a game as history: both teams to score, draw no bet, double chance, and the 1st half result, total and goal handicap, for the Premier League, La Liga, Serie A, the Bundesliga, Ligue 1, MLS and the Champions League. Pass game_id (from get_schedule or list_games) and market. For each sportsbook it returns the opening line (the first one we captured) and the closing line (the last one before the game started), each as the list of outcomes with their point and American price, plus captured_at and minutes_before_start (negative when the last capture came after our scheduled start, which the sportsbooks' listed start can run past). Most books were captured once, so opening and closing are often the same line. Held for the larger sportsbooks only: both teams to score from May 2023, the other markets from August 2023 (later in some leagues); not every match has every market. Each match's lines are added the morning after it is played. Costs 10 credits a call; a game with no lines is refunded. Set estimate_only to get the price without being charged. For the full-game moneyline, spread and total use get_odds. Prices are market information; no tool places, accepts or tracks wagers.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "game_id": "<game_id>",
      "market": "<market>"
    },
    "name": "get_market_odds"
  }
}

Input Schema

NameRequiredDescriptionDefault
leagueNoLeague. Defaults to soccer. One of: soccer, mls, laliga, seriea, bundesliga, ligue1, ucl.
marketYesThe market: btts (both teams to score: Yes or No), draw_no_bet (draw no bet: home or away, a draw voids it), double_chance (double chance: two of home, draw and away (e.g. Arsenal or Draw)), h2h_h1 (1st half result: home, draw or away), totals_h1 (1st half total goals), spreads_h1 (1st half goal handicap)
game_idYesGame id from get_schedule or list_games.
bookmakerNoOne bookmaker key, e.g. draftkings, fanduel, pinnacle.
estimate_onlyNoReturn what this call would cost, without charging or running it.

Output Schema

NameRequiredDescriptionDefault
noteNo
toolNo
booksYes
countYes
labelYes
marketYes
creditsNo
game_idYes
estimate_onlyNo
scheduled_startYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses cost (10 credits), the refund rule for games with no lines, data availability windows (May/August 2023 onward, later in some leagues), the next-morning ingestion cadence, and that opening/closing are often identical because most books are captured once. It also explains the negative minutes_before_start edge case. It stops short of describing pagination or response size, but the behavioral picture is unusually complete.

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?

Purpose and the sibling distinction are front-loaded, and the dense middle sentences each carry distinct operational facts (capture semantics, coverage windows, cost). It is long and slightly run-on, but very little is redundant.

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?

An output schema exists, yet the description still sketches the return shape (opening/closing lines, outcomes with point and American price, captured_at, minutes_before_start), which helps interpretation. Combined with coverage caveats, cost and refund rules, nothing an agent needs before calling is missing.

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%, including per-enum explanations for all six market values, so the schema already carries the parameter meaning. The description reinforces the game_id source and estimate_only behavior but adds little that the schema does not already state, and never mentions bookmaker or the league default. 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?

The description names a specific resource (extra betting markets as history) and enumerates the exact markets covered (both teams to score, draw no bet, double chance, 1st half result/total/handicap) and the leagues. It explicitly separates itself from get_odds, which covers full-game moneyline, spread and total, so an agent can route correctly without opening either schema.

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?

It states when to use it (extra markets) and when not to (full-game moneyline/spread/total go to get_odds), tells the agent where game_id comes from (get_schedule or list_games), and explains the estimate_only path for pricing a call without being charged. Alternatives and conditions are explicit rather than inferred.

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.