Skip to main content
Glama

football_find_value_bets

Read-onlyIdempotent

Surfaces gaps between model win probabilities and market odds, flagging value bets where the model's edge exceeds a minimum threshold.

Instructions

Surface the largest gaps between the model's win probability and the market.

De-vigs each market's 1X2 decimal odds (removes the margin so implied probabilities sum to 1) and compares them to this server's own match-outcome probabilities — the same Elo/Poisson path football_match_predictor uses. Where the model probability exceeds the de-vigged market probability by at least min_edge, the outcome is flagged with its edge and the model's fair odds.

Args: team: Optional team name to filter events (case-insensitive substring, matched against both sides). Omit to scan every WC 2026 odds event. min_edge: Minimum edge (model_prob - devigged_market_prob), 0..1. Default 0.05 (5 percentage points).

Returns: data.value_bets: list of {event_id, home, away, outcome, model_prob, fair_odds, market_odds, edge, bookmaker}, sorted by edge descending. data.events_analysed: events with both teams rated (model-comparable). meta.estimated: true. meta.is_stale reflects the odds freshness.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
teamNoOptional team name to filter events (case-insensitive substring, matched against both sides). Omit to scan every WC 2026 odds event.
min_edgeNoMinimum edge (model_prob - devigged_market_prob), 0..1. Default 0.05 (5 percentage points).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo
metaNo
errorNo
Behavior4/5

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

Annotations already indicate readOnlyHint, idempotentHint, and destructiveHint. Description adds details about de-vigging process, comparison to model probabilities, sorting by edge, and freshness indicator (meta.is_stale). No contradictions.

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?

Description is well-structured with purpose, methodology, args, and returns. Slightly verbose but front-loaded with main purpose. Could be more concise, but effective.

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 complexity of value bet detection, description covers methodology, de-vigging, comparison, and output format. Output schema exists, so return values are detailed. Context about WC 2026 odds is provided.

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 baseline 3. Description adds meaning beyond schema: 'team' is case-insensitive substring matched against both sides, 'min_edge' clarified as range 0..1 with default 0.05.

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?

Description clearly states 'Surface the largest gaps between the model's win probability and the market.' It explains de-vigging and comparison to model probabilities, and distinguishes from sibling 'football_match_predictor' by noting it uses the same underlying model.

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?

Description explains when to use (when model probability exceeds market probability by min_edge) and provides default thresholds. It does not explicitly state when not to use, but sibling tools like 'football_build_accumulator' and 'football_match_predictor' indicate alternative contexts.

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/Ninjabeam20/SportIQ-MCP'

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