Skip to main content
Glama
DanielTomaro13

sportsdata-mcp

theoddsapi_event_odds

Read-onlyIdempotent

Retrieve odds for a single event, including player props and additional markets. Specify sport and event ID to get bookmaker odds.

Instructions

Odds for ONE event, including player props and other markets not available on the competition-wide call.

Returns: {id, sport_key, commence_time, home_team, away_team, bookmakers:[{key, title, markets:[{key, outcomes:[{name, price, point, description}]}]}]} — a single object, unlike the competition call's array; description carries the player name on prop markets

NOTE: this shape is from the vendor's documentation and has NOT been verified against a live response (we hold no key for this provider). Treat it as approximate — inspect the actual payload before relying on a field name.

Example: One event's markets {"sport": "soccer_epl", "eventId": "", "regions": ["au"], "markets": ["h2h"]}

Auth: needs your own key in THE_ODDS_API_KEY.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sportYessport_key. Required — part of the URL path.
eventIdYesEvent id from theoddsapi_odds or theoddsapi_events. Required — part of the URL path.
marketsNoIncludes player-prop markets here, e.g. player_pass_tds.
regionsNoBookmaker regions.
oddsFormatNoPrice format. One of: decimal, american.decimal
Behavior5/5

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

Beyond the readOnly and idempotent annotations, the description discloses the return structure, warns that the shape is unverified and approximate, advises inspecting the actual payload, and notes the auth key requirement. This is honest and thorough about reliability.

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 well-structured with clear sections: purpose, return schema, reliability note, example, and auth. It is slightly long but every part adds value—especially the inline return schema and the unverified-payload warning.

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?

Despite having no output schema, the description compensates with an inline return schema, an example, an explicit reliability caveat, and auth requirements. All parameters are covered by the schema. The tool is effectively fully specified for its purpose.

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?

The input schema already describes all five parameters with 100% coverage. The description adds an example call and clarifies the eventId source, but no additional parameter-specific semantics beyond what the schema provides.

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 'Odds for ONE event' and distinguishes it from the 'competition-wide call' (theoddsapi_odds). It specifies the resource (event odds) and scope (single event, including player props), making the purpose unambiguous.

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 implies when to use this tool: when you need single-event odds, player props, or markets not available on the competition-wide call. It contrasts the single-object return with the competition call's array, but does not explicitly state when not to use it or list alternative tool names.

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/DanielTomaro13/sportsdata-mcp'

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