Skip to main content
Glama

sportiq-mcp

by io.github.Ninjabeam20

cricket_get_live_odds

Read-onlyIdempotent

Return live market head-to-head odds for upcoming/live IPL matches.

Sourced from The Odds API (requires THEODDS_KEY). Without a key the call returns a clean ALL_SOURCES_FAILED envelope rather than crashing.

Args: team: Optional team name to filter events (case-insensitive substring, matched against both sides). Omit to return every IPL event. The Odds API uses its own opaque event ids, so a CricAPI match_id cannot be resolved to an event yet — filtering is by team name.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
teamNoOptional team name to filter events (case-insensitive substring, matched against both sides). Omit to return every IPL event. The Odds API uses its own opaque event ids, so a CricAPI match_id cannot be resolved to an event yet — filtering is by team name.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo
metaNo
errorNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the strong annotations, the description discloses critical runtime behavior: it requires THEODDS_KEY, returns a clean ALL_SOURCES_FAILED envelope instead of crashing when the key is missing, and exposes meta.source to indicate the odds adapter or cache:stale. This is exactly the kind of behavioral context an agent needs beyond readOnly/idempotent hints.

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 description is front-loaded with the core purpose, followed by essential dependency/error behavior, then parameter and return details in clear sections. Every sentence earns its place, and the formatting makes it easy for an agent to parse quickly.

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?

With an output schema available, the description still takes care to explain the return shape (events with bookmakers and decimal h2h prices) and the meta.source field. It also covers the prerequisite key, failure envelope, and filtering caveats, leaving no important operational gap for an agent invoking this tool.

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 Args section essentially repeats the schema's team parameter explanation. Since the schema already fully documents the parameter, the description adds no additional semantic value beyond what's already structured, giving the baseline score of 3.

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 uses a specific verb and resource: 'Return live market head-to-head odds for upcoming/live IPL matches.' This clearly distinguishes the tool from the many sibling tools, such as football_get_odds or cricket_find_value_bets, by scope (IPL) and data type (h2h odds).

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?

The description gives clear context: it is for IPL live/upcoming h2h odds, with optional team filtering and a note about The Odds API's opaque event ids. It does not explicitly name sibling alternatives or state when not to use them, but the intended use is clear enough for an agent to select it correctly.

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

All sportiq-mcp toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation3/5

Sport prefixes make the three domains easy to separate, and most tools have clear purposes. However, several tools overlap: football_match_predictor vs football_xg_model, f1_head_to_head_pace vs f1_race_pace_compare, and the cricket fantasy tools (build_dream11, captain_recommendation, differential_picks) all require careful reading to avoid misselection.

Naming Consistency4/5

The sport prefix + snake_case pattern is consistent and retrieval tools uniformly use get_, which creates predictability. The main deviation is that many analysis/model tools are noun phrases rather than verb_noun (cricket_head_to_head, football_knockout_path, f1_tyre_degradation), but they remain readable and scoped.

Tool Count2/5

44 tools is well above the 25+ threshold for a single server and will strain agent context and tool-selection quality. Each sport block is individually reasonable at 13-15 tools, but combining three sports plus cross-sport and health utilities makes the overall surface too large.

Completeness3/5

Core workflows are broadly covered: live data, schedule/standings, match prediction, tournament simulation, fantasy help, and strategy analysis exist for each sport. However, there are notable dead ends: cricket_player_form_index needs a player_id no exposed tool returns, football_get_match_stats requires an API-Football numeric ID not mapped anywhere, and f1_get_lap_times references a stints endpoint that is not exposed as a tool.

Resources