SportIQ

football_get_odds

Read-onlyIdempotent

Retrieves 1X2 bookmaker odds for World Cup 2026 events and filters by team, helping users compare market prices for a specific fixture.

Instructions

Return market head-to-head odds for any World Cup 2026 events the odds feed still lists.

Sourced from The Odds API (requires THEODDS_KEY). Without a key the call returns a clean ALL_SOURCES_FAILED envelope rather than crashing. The tournament ended with the 2026-07-19 final, so the feed is normally empty.

Args: team: Optional team name to filter events (case-insensitive substring, matched against both sides). Omit to return every WC event.

Returns: data.events: list of {event_id, home, away, commence_time, bookmakers: [{name, home, draw, away, last_update}]} with decimal 1X2 prices per bookmaker. meta.source: adapter that served the data (theodds / cache:stale).

Input Schema

Name	Required	Description	Default
`team`	No	Optional team name to filter events (case-insensitive substring, matched against both sides). Omit to return every WC event.

Output Schema

Name	Required	Description	Default
`data`	No
`meta`	No
`error`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1Jul 10, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Annotations already cover read-only, idempotent, open-world, and non-destructive behavior, and the description adds meaningful context beyond them: THEODDS_KEY is required, missing keys return an ALL_SOURCES_FAILED envelope, and meta.source can indicate theodds or cache:stale. These are exactly the behavioral details an agent needs before invoking the tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

The first sentence front-loads purpose and scope, and the subsequent sections efficiently cover key requirements, failure behavior, arguments, and return shape. The structure is clear and every section adds operational value.

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 the tool has an output schema, the description does not need to explain return values in depth, yet it still covers the important edge cases: missing API key, empty feed after tournament end, and optional filtering. It is complete for correct invocation.

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%, and the description’s team-argument explanation largely repeats the schema text rather than adding new semantics. With the schema already documenting the optional filter, a baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: returns market head-to-head odds for World Cup 2026 events. Scope is clear, but it does not explicitly differentiate itself from football siblings such as football_find_value_bets or football_build_accumulator.

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

Usage Guidelines3/5

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

It gives useful operational context, including the key requirement, the normally empty feed after the final, and the team-filter behavior. However, it does not explicitly say when to use this instead of sibling odds-related tools or when not to use it.

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

Deploy Server