EndzoneAPI

Odds

get_odds

Read-onlyIdempotent

Use for betting lines. Pass game_id for one game (10 credits): the consensus closing spread and total (every game since 1999; moneyline every game since 2010) plus each sportsbook's closing line from the 2014 season (4-9 books for 2014-2019, closing only) and per-bookmaker opening, closing and latest lines from the 2020 season (up to 8 books, including Pinnacle). Or pass season (optionally team) for a season of per-book closing lines in one call, with final scores and the consensus close, at 10 credits per game returned, 100 games a page by default (up to 500); each book's line is an array in the order given by columns. Each line carries a source field (one value for the 2014-2019 closing lines, another from 2020); a season answer lists each game's sources. For consensus closing lines only, get_games returns a whole season for 5 credits. Set estimate_only to get the price without being charged. Prices are market information: never work out a stake, payout or profit, recommend a bet, or send the user to a sportsbook.

Input Schema

Name	Required	Description
`team`	No	With season: only this team's games (e.g. KC).
`limit`	No	With season: games per page (default 100, max 500).
`offset`	No	With season: page offset; use next_offset from the previous page.
`season`	No	Season year for a whole season of per-book lines, e.g. 2026. Used when game_id is not set.
`game_id`	No	Game id, e.g. 2026_01_KC_BUF. Omit and pass season for a whole season.
`bookmaker`	No	Bookmaker key (draftkings, fanduel, betmgm, espnbet, pinnacle, bovada, betonlineag, mybookieag; for 2014-2019 also westgate, caesars, wynn, unibet, 5dimes, sportsbettingag and others)
`estimate_only`	No	Return what this call would cost, without charging or running it.
`snapshot_type`	No	Single game: one snapshot type (default all). Season: opening or closing (default closing).

Output Schema

Name	Required	Description	Default
`note`	No
`tool`	No
`books`	No
`count`	No
`games`	No
`season`	No
`columns`	No
`credits`	No
`game_id`	No
`kickoff`	No
`away_team`	No
`home_team`	No
`next_offset`	No
`total_games`	No
`estimate_only`	No
`snapshot_type`	No
`bookmaker_count`	No
`credits_per_game`	No
`consensus_closing`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 8, 2026

changedInput schema / properties / bookmaker / description

Previous value: -"Bookmaker key (draftkings, fanduel, betmgm, espnbet, pinnacle, bovada, betonlineag, mybookieag)"New value: +"Bookmaker key (draftkings, fanduel, betmgm, espnbet, pinnacle, bovada, betonlineag, mybookieag; for 2014-2019 also westgate, caesars, wynn, unibet, 5dimes, sportsbettingag and others)"

Changed1 schema field changedOct 5, 2026

changedInput schema / properties / bookmaker / description

Previous value: -"Bookmaker key (draftkings, fanduel, betmgm, espnbet)"New value: +"Bookmaker key (draftkings, fanduel, betmgm, espnbet, pinnacle, bovada, betonlineag, mybookieag)"

Changed20 schema fields changedSep 27, 2026

changedInput schema / properties / bookmaker / description

Previous value: -"Bookmaker key (draftkings, fanduel, betmgm, caesars, espnbet)"New value: +"Bookmaker key (draftkings, fanduel, betmgm, espnbet)"

addedInput schema / properties / estimate_only

Added value: +{
+  "description": "Return what this call would cost, without charging or running it.",
+  "type": "boolean"
+}

changedInput schema / properties / game_id / description

Previous value: -"Game id, e.g. 2026_01_KC_BUF"New value: +"Game id, e.g. 2026_01_KC_BUF. Omit and pass season for a whole season."

addedInput schema / properties / limit

Added value: +{
+  "description": "With season: games per page (default 100, max 500).",
+  "maximum": 500,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / offset

Added value: +{
+  "description": "With season: page offset; use next_offset from the previous page.",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / season

Added value: +{
+  "description": "Season year for a whole season of per-book lines, e.g. 2026. Used when game_id is not set.",
+  "type": [
+    "string",
+    "number"
+  ]
+}

changedInput schema / properties / snapshot_type / description

Previous value: -"Return only one snapshot type. Default returns opening, closing, and latest per book."New value: +"Single game: one snapshot type (default all). Season: opening or closing (default closing)."

addedInput schema / properties / team

Added value: +{
+  "description": "With season: only this team's games (e.g. KC).",
+  "type": "string"
+}

removedInput schema / required
```
Removed value: -[
-  "game_id"
-]
```

addedOutput schema / properties / columns

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / credits
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / credits_per_game
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / estimate_only
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / games

Added value: +{
+  "items": {
+    "additionalProperties": {},
+    "propertyNames": {
+      "type": "string"
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / next_offset

Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}

addedOutput schema / properties / season
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / snapshot_type
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / tool
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / total_games
```
Added value: +{
+  "type": "number"
+}
```

removedOutput schema / required

Removed value: -[
-  "game_id",
-  "home_team",
-  "away_team",
-  "kickoff",
-  "consensus_closing",
-  "books",
-  "bookmaker_count",
-  "count"
-]

First observedSep 27, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), the description discloses credit pricing (10 credits per game, 5 via get_games), pagination defaults (100 per page, max 500), historical coverage boundaries (1999 for spread/total, 2010 for moneyline, 2014/2020 book eras), the source field semantics, and estimate_only pricing behavior. This is rich behavioral context an agent cannot get from the structured fields alone.

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 purpose is front-loaded in the first sentence, and nearly every clause carries substantive information about modes, costs, or coverage. The main weakness is structure: the second sentence is a very long run-on with nested parentheticals that is harder to parse than it needs to be.

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?

Given the complexity (8 parameters, two distinct modes, credit pricing, historical book coverage), the description covers everything an agent needs to call it correctly, including pricing, pagination, mode defaults, and usage constraints. An output schema exists, so return-value explanation is appropriately delegated to it.

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 cross-parameter meaning: game_id vs. season mode selection, team/limit/offset only applying with season, snapshot_type defaults differing by mode, and credit costs tied to the chosen mode. It also clarifies array ordering for per-book lines, though it does not add much beyond the already-detailed schema descriptions for individual fields.

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 opens with a specific purpose (betting lines) and then precisely enumerates the two retrieval modes (single game via game_id vs. whole season via season), including data coverage by era. It explicitly distinguishes itself from the sibling get_games by noting that get_games only returns consensus closing lines for 5 credits, so an agent can route correctly without opening schemas.

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?

It gives clear mode-selection guidance (pass game_id for one game, or season optionally with team for a season) and names get_games as the cheaper alternative for consensus-only needs. It also states a firm usage constraint about not computing stakes or recommending bets. However, it does not explicitly exclude adjacent siblings like get_line_movement, get_player_props, or get_alt_lines, leaving some routing ambiguity.

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

All EndzoneAPI tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Odds

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources