Skip to main content
Glama
This connector has been deprecated

Moved to a server instead of a connector

Game probabilities

get_game_probabilities
Read-onlyIdempotent

Use for what the market thinks of one game, not any one book's price: the average implied probability (margin in) and the fair probability (margin out) for the moneyline, each puck line and each total, with how many books each rests on. Only identical lines are combined. Each book's last pre-game prices by default (snapshot_type reads latest until the start, closing after it); opening on request. For each book's prices use get_odds. Costs 5 credits. Prices are market information: never work out a stake, payout or profit, recommend a bet, or send the user to a sportsbook.

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>"
    },
    "name": "get_game_probabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault
game_idYesGame id, e.g. 2024020001.
snapshot_typeNoclosing (default): each book's last pre-game price so far. opening: each book's first.

Output Schema

NameRequiredDescriptionDefault
noteNo
toolNo
countYes
methodYes
totalsYes
creditsNo
game_idYes
spreadsYes
away_teamYes
home_teamYes
moneylineYes
estimate_onlyNo
snapshot_typeYes
scheduled_startYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond read-only annotations, the description explains aggregation rules ('Only identical lines are combined'), snapshot timing semantics, book-count context, credit cost, and compliance restrictions. These are material behavioral details an agent would not get from the 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.

Conciseness4/5

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

The description is dense and front-loads the main use case, with no clearly wasted sentences. It is slightly semicolon-heavy and could be easier to scan, but the detail is purposeful.

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?

Given that an output schema exists and annotations already cover safety traits, the description supplies the remaining operational context: aggregation scope, default snapshot behavior, cost, and usage limits. Nothing essential for correct invocation appears missing.

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?

Schema coverage is already 100%, so the baseline is high. The description still adds useful meaning for snapshot_type by explaining that closing is the default last pre-game price and that opening must be requested, which goes beyond the schema's shorter wording.

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 states a precise purpose: average implied and fair probabilities for a game's moneyline, puck lines, and totals, including book counts. It explicitly distinguishes this from individual book prices and names the sibling tool get_odds for that alternative.

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 clearly says when to use this tool versus get_odds, explains the default snapshot behavior, notes that opening prices are available on request, and discloses the 5-credit cost. The exclusion against stake/payout/bet advice is also explicit.

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.

Resources