Skip to main content
Glama

Live Sports Scores & Betting Odds MCP Server

get_odds

Return betting lines for a league's current scoreboard: point spread, over/under total, and home/away moneyline (single-book, DraftKings via ESPN), plus each team's win/loss record and the game status. Call with a league token (nfl, nba, nhl, mlb, epl, "la liga", ncaaf, ucl, ...). Lines appear once a game is posted by the book and are null before then. Keyless, free. Bulk/scheduled odds feeds are in see_also.

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": {
      "league": "<league>"
    },
    "name": "get_odds"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax games to return (default 50, max 200).
leagueYesLeague token: nfl, nba, wnba, nhl, mlb, ncaaf, ncaam, ufc, epl, "la liga", bundesliga, "serie a", ligue1, ucl, uel, mls — or a raw ESPN path like "soccer/esp.1". Call list_odds_leagues for all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the data source and single-book limitation (DraftKings via ESPN), the auth/cost model (keyless, free), and the null-before-posting behavior that would otherwise cause false negatives. It omits freshness/caching or rate-limit behavior, which is the main remaining gap for a live-data tool.

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?

Three tightly packed sentences, front-loaded with what is returned before invocation details and caveats. The only wasted element is the dangling 'see_also' reference, which points at nothing the agent can resolve.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter, no-output-schema, no-annotation tool, the description covers the returned fields, the null condition, the source, and that it is keyless — enough to call it correctly. Minor gaps are whether 'current scoreboard' means today only and how the limit interacts with ordering.

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%, so both parameters are already documented, and the description largely repeats the league token list while adding 'la liga' quoting nuance. It adds nothing about the limit parameter (default, max, ordering of returned games), so it neither compensates for nor meaningfully extends the schema.

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 verb+resource ('Return betting lines for a league's current scoreboard') and then enumerates the exact payload: point spread, over/under, moneyline, team records, and game status. It also distinguishes itself from bulk/scheduled odds feeds, so an agent can tell it apart from siblings like list_odds_leagues without opening any 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?

It gives clear invocation context ('Call with a league token') with concrete token examples, and states the data-availability condition ('Lines appear once a game is posted by the book and are null before then'). The pointer to alternatives is weak — 'Bulk/scheduled odds feeds are in see_also' references an undefined field rather than naming a sibling tool — so there is no crisp when-not-to-use routing.

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.