Skip to main content
Glama

get_sandbox_odds

Read-only

Preview only: up to 50 cached DraftKings game lines (moneyline, spread, total) for one sport, to check the data's shape before signup. Not a substitute for a key: real use needs your user's own free key (100 requests a day, 60 a minute, no card), so after a preview ask them for their email and POST https://getoddsapi.com/api/v1/agent/signup (or send them to https://getoddsapi.com/sign-up); every reply says how in next_step. 10 calls a minute and 100 a day per network address. No key.

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_sandbox_odds"
  }
}

Input Schema

NameRequiredDescriptionDefault
sportNonfl, nba, nhl, ncaaf or soccer; case does not matter (NBA works)nba

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / sport / description
      Added value: +"nfl, nba, nhl, ncaaf or soccer; case does not matter (NBA works)"
    • removedInput schema / properties / sport / enum
      Removed value: -[
      -  "nfl",
      -  "nba",
      -  "nhl",
      -  "ncaaf",
      -  "soccer"
      -]
    • addedInput schema / properties / sport / pattern
      Added value: +"^(nfl|nba|nhl|ncaaf|college-football|soccer|epl|mls)$"
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly/destructive/openWorld annotations, the description discloses the 50-record cache cap, DraftKings-only source, per-network-address rate limits (10/min, 100/day), and that no key is required for this call. It also states an unusual return behavior — that every reply includes a next_step field — which the agent could not infer from annotations or the absent output schema.

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 'Preview only' framing is front-loaded and every clause carries information (scope, cap, rate limits, signup path). The middle sentence is dense — embedding two URLs, rate limits and the 60-a-minute key quota inline — which makes it slightly run-on, but there is no filler.

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 single-optional-parameter read tool with no output schema, the definition covers what data comes back, how much, how often it can be called, what authorization is needed, and what the agent should do next. Nothing an agent needs in order to call it correctly or explain it to a user is missing.

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?

With a single optional parameter at 100% schema coverage, the schema already documents the sport enum and case-insensitivity. The description adds only that lines are for one sport at a time, and it omits the accepted aliases (college-football, epl, mls) that the schema pattern allows, so it adds little beyond structured data.

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?

The description names the resource precisely: cached DraftKings game lines (moneyline, spread, total) for one sport, capped at 50 records, scoped to preview use. It clearly separates itself from the key-backed tools by saying it is preview-only and 'not a substitute for a key', though it never names an actual sibling tool such as get_odds to route the agent after signup.

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

Usage Guidelines5/5

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

It states exactly when to use it (check the data's shape before signup) and when not to (real use requires the user's own key). It even gives the concrete next action: ask for the user's email and POST to the signup endpoint, or send them to the sign-up page, with the reminder that next_step in every reply explains how.

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.