Skip to main content
Glama
Sign In
Odds-API MCP Server

Odds-API MCP Server

Official
by odds-api-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Outright odds

get_outright_odds
Read-onlyIdempotent

Fetches outright tournament odds from selected bookmakers, filtered by market and runner limit, so users can compare prices for golf winners, top finishes, and make-cut markets.

Instructions

Prices for one outright tournament from the named bookmakers. Golf markets: Winner, Top 5, Top 10, Top 20 (boundary ties under dead-heat rules), Top 5 (Incl. Ties), Top 10 (Incl. Ties), Top 20 (Incl. Ties) (ties paid in full) and Make Cut (only events with a cut). Runners carry label, participantId and odds (+ layOdds on exchanges), or yes/no for Make Cut, sorted shortest price first. A full field is large: pass markets and maxRunners. Needs the Outrights add-on: a 403 means the key does not have it, so tell the user the message and do not retry.

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": {
      "id": "<id>",
      "bookmakers": "<bookmakers>"
    },
    "name": "get_outright_odds"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesOutright id from list_outrights
marketsNoOptional comma-separated market names to keep, e.g. 'Winner,Top 10 (Incl. Ties)' (filtered after the call)
bookmakersYesComma-separated bookmaker names, max 30 (e.g. 'Bet365,SingBet'). Must be in the key's selection (get_selected_bookmakers).
maxRunnersNoOptional: keep only the first N runners (shortest prices) per market

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.8.3

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare read-only/idempotent/open-world; the description adds real behavior the agent could not infer: runners are sorted shortest price first, layOdds appear on exchanges, Make Cut returns yes/no, ties are handled under dead-heat versus paid-in-full rules, and the add-on gate returns 403 with no retry. That is exactly the beyond-annotation context this dimension rewards.

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-loads what the tool returns, then the market taxonomy, then the practical mitigations and error handling. The long parenthetical market list is dense but each clause carries distinct information; only the market enumeration could be trimmed slightly.

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?

There is no output schema, yet the description documents the return shape (label, participantId, odds, layOdds, yes/no for Make Cut, sort order), the sport-specific market rules, the size hazard, and the failure mode. An agent can call it correctly without consulting anything else.

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; the description adds rationale rather than syntax by explaining that a full field is large and that markets and maxRunners should be passed to tame it. It does not add new format detail (the 30-bookmaker cap and post-call filtering are already in the schema), so it lands just above baseline.

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 resource and scope: prices for one outright tournament from named bookmakers, then enumerates the exact golf markets returned. That is enough for an agent to separate it from get_odds (event markets), list_outrights (enumeration) and get_outright_results without opening a schema.

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?

Gives concrete operating guidance: pass markets and maxRunners because a full field is large, and the Outrights add-on is required, with an explicit instruction to report a 403 and not retry. It stops short of explicitly naming alternatives (get_odds, list_outrights) as the when-to-use routing rule, but the practical context is clear.

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

Deploy Server

Other Tools