Skip to main content
Glama

FastballAPI

Odds

get_odds
Read-onlyIdempotent

Use for betting lines: each sportsbook's moneyline, run line and total for a game (opening and closing per book from July 2020; before that, each book's final pregame line only), with implied probabilities and, for finished games, whether the favourite won and the total went over against the median close. Pass game_id for one game (5 credits) or date for a day's games (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
dateNoA day's games, YYYY-MM-DD (US Eastern).
leagueNoLeague. Defaults to mlb. One of: mlb, ncaabase.
game_idNo

Output Schema

NameRequiredDescriptionDefault
noteNo
toolNo
countNo
gamesNo
creditsNo
estimate_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so safety is covered. The description adds genuine context beyond that: the July 2020 historical cutoff where only the final pregame line exists, the presence of implied probabilities, and settlement flags for finished games. It also correctly notes no wagering action is taken. Missing credit cost for league-only or empty calls.

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-loaded with the resource and field list, then pricing, then a scope disclaimer — logical ordering. Dense but each clause carries information; the parenthetical historical caveat is long but necessary.

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

Completeness3/5

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

Output schema exists so return values needn't be explained, and the description covers history and pricing well. However with three optional parameters and several odds-related siblings, the definition does not make selection unambiguous — the biggest gap for a zero-required-param 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?

game_id and league semantics are already in the schema (league has full description and enum; date is documented with timezone). The description only implies that game_id scopes to one game and date to a day's slate, plus a cost per path, which is modest added meaning over 67% coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource (each sportsbook's moneyline, run line and total for a game) with scope detail — per-book opening and closing lines, with historical cutoff. Clear what data it returns, though it never explicitly says how it differs from siblings like get_market_odds or get_alt_lines.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives cost-based selection between the game_id and date paths, which is useful, but no guidance on when to prefer this over get_market_odds, get_line_movement or get_alt_lines. The agent must infer the boundary from names alone.

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.