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 results

get_outright_results
Read-onlyIdempotent

Fetch final results for a single outright tournament, including each golfer's position, cut/status, and market winners; returns empty until settled and requires Outrights add-on.

Instructions

Final results for one outright tournament: each golfer's position (shared when tied, null when cut, withdrawn or disqualified), madeCut and status, plus winners per market (Winner, Top N, Top N (Incl. Ties), Make Cut). Empty until the tournament is settled. Dead-heat and each-way terms are the bookmaker's rules. Needs the Outrights add-on (403 without it: tell the user, 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>"
    },
    "name": "get_outright_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesOutright id from list_outrights

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.8.3

TDQS

A4.5/5.0
Behavior5/5

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

Annotations cover read-only/idempotent safety, but the description adds substantial context beyond them: the empty-until-settled state, null semantics for cut/withdrawn/disqualified, how ties are represented, that dead-heat and each-way terms follow bookmaker rules, and the 403 add-on behavior with a no-retry instruction.

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?

Four compact sentences, each carrying distinct information — return shape, empty state, settlement rules, and the add-on error path — with the core purpose front-loaded and no padding.

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 no output schema, the description carries the burden of describing returns and does so explicitly (position with tie/cut/null handling, madeCut, status, per-market winners). Error handling and prerequisite state are also covered, leaving nothing essential missing for a single-parameter read 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 coverage is 100% and the single parameter already documents 'Outright id from list_outrights'. The description reinforces the 'one outright tournament' scoping but adds no new syntax, format, or validation detail beyond the schema, so the baseline of 3 applies.

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?

Opens with a specific verb+resource ('Final results for one outright tournament') and enumerates exactly what is returned: per-golfer position, madeCut, status, and winners per market type. This reads clearly as distinct from the odds/list siblings (get_outright_odds, list_outrights).

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 timing guidance ('Empty until the tournament is settled') and precise failure handling ('Needs the Outrights add-on (403 without it: tell the user, do not retry)'), which steers the agent away from useless retries. It does not explicitly name when to prefer get_outright_odds or list_outrights, so a sibling-comparison sentence is the only gap.

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