StrikerAPI

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 (home, draw and away), each handicap 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

Name	Required	Description
`league`	No	League. Defaults to soccer. One of: soccer, mls, laliga, seriea, bundesliga, ligue1, ucl, championship, nwsl, ligamx, uel, uecl, eredivisie, primeira, scotland, brazil, argentina.
`game_id`	Yes	Game id, e.g. 401879246.
`snapshot_type`	No	closing (default): each book's last pre-game price so far. opening: each book's first.

Output Schema

Name	Required	Description	Default
`note`	No
`tool`	No
`count`	Yes
`method`	Yes
`totals`	Yes
`credits`	No
`game_id`	Yes
`spreads`	Yes
`away_team`	Yes
`home_team`	Yes
`moneyline`	Yes
`estimate_only`	No
`snapshot_type`	Yes
`scheduled_start`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 7, 2026
- changedInput schema / properties / game_id / description
```
Previous value: -"Game id, e.g. 740847."New value: +"Game id, e.g. 401879246."
```
AddedNov 7, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), and the description adds real value on top: the aggregation rule ('only identical lines are combined'), the snapshot semantics (latest until start, closing after), and a cost of 5 credits. It also discloses a compliance constraint — no stake/payout computation, no recommendations, no sportsbook referral — which meaningfully shapes how an agent should present the output.

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?

Front-loaded with the core purpose and alternative routing, then defaults, cost, and compliance — a sensible order with no filler. The opening sentence is dense to the point of being slightly hard to parse on first read, which keeps it from a 5.

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, so return structure need not be described; the description instead covers what an agent could not infer: aggregation scope, cross-book counting, snapshot defaults, credit cost, and usage restrictions. Nothing needed to call this correctly is 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 100%, so the baseline is 3, but the description adds genuine meaning for snapshot_type by explaining that it resolves to latest-until-start and switches to closing after the game begins, which the schema's 'closing (default)' does not convey. league and game_id get no extra treatment, but they need none.

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: aggregate market implied probability (margin in) and fair probability (margin out) for moneyline, each handicap and each total, plus the number of books behind each. It explicitly contrasts itself with per-book pricing, so an agent can separate it from get_odds and get_market_odds 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?

Gives an explicit use case ('what the market thinks of one game, not any one book's price') and routes the alternative case to a named sibling: 'For each book's prices use get_odds.' It also states the default snapshot behavior and that opening odds are available on request, so the agent knows which selector to pass.

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

All StrikerAPI tools Inspect

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.