Skip to main content
Glama

Odds

get_odds
Read-onlyIdempotent

Use for betting lines: each posted sportsbook's opening, closing and current moneyline for both fighters, with implied probabilities and the total-rounds line. Opening and closing lines start with the UFC cards of June 2020; a median of 5 to 7 books per fight (some fights since mid-2024 have only one book). Pass bout_id for one fight (5 credits) or event_id for a whole card (10 credits). Prices are market information; no tool places, accepts or tracks wagers.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_odds"
  }
}

Input Schema

NameRequiredDescriptionDefault
leagueNoLeague. Defaults to mma. One of: mma, pfl, bellator.
bout_idNoOne fight.
event_idNoA whole card.

Output Schema

NameRequiredDescriptionDefault
noteNo
toolNo
boutsNo
countNo
creditsNo
estimate_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing data-coverage constraints (opening/closing lines only from June 2020 UFC cards onward, a median of 5-7 books per fight, some post-mid-2024 fights with a single book) and per-call credit costs. It also clarifies the domain boundary — prices are market information and no tool places, accepts, or tracks wagers — which prevents a costly misinterpretation.

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?

Front-loads the purpose in the opening clause, then layers coverage caveats, cost mechanics, and a scope disclaimer. Every sentence carries distinct information with no redundant restatement of the title or schema.

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?

For a read-only pricing lookup with a full schema and an output schema, the description covers everything an agent needs: what is returned, historical coverage limits, cost per calling pattern, and the boundary that this is informational only. Return-format detail is correctly delegated to the output schema.

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, but the description adds real meaning on top: it attaches credit costs to bout_id versus event_id, letting an agent weigh parameter choice economically. It doesn't elaborate on the league enum beyond the schema's own text.

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?

Names a specific resource (sportsbook betting lines) and enumerates exactly what is returned: opening/closing/current moneyline per book for both fighters, implied probabilities, and the total-rounds line. This is distinct from siblings like get_line_movement, so an agent can tell them apart 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 explicit selection guidance: pass bout_id for one fight (5 credits) or event_id for a whole card (10 credits), which lets an agent choose scope on cost grounds. It lacks an explicit statement of when to prefer a sibling such as get_line_movement, so it stops short of full when/when-not coverage.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.