Skip to main content
Glama

get_odds

Read-only

Read stored DraftKings-via-ESPN odds. Preserve capture time and source identifiers. Offset pages are not a frozen snapshot.

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
limitNo
sportNo
marketNo
offsetNo
event_idNo
fresh_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnly, non-destructive, and closed-world, so the safety profile is covered by structured data. The description adds two genuinely useful behavioral facts beyond that: results carry a capture time and source identifiers that callers should retain, and offset paging is not a frozen snapshot (pages may reflect different capture instants). However, nothing is said about sort order, empty-result behavior, or the relationship between stored and fresh data.

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 terse sentences with the core action front-loaded and no filler. The compression costs some clarity — 'Preserve capture time and source identifiers' is ambiguous about whether it is a return-value contract or an instruction to the caller.

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

Completeness2/5

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

For a 6-parameter, zero-coverage, no-output-schema tool sitting among a dozen odds-related siblings, the definition is too thin: parameter meaning and sibling routing are both left to inference. The paging caveat is a good start but not enough to make the tool callable with confidence.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 6 parameters, and the description compensates for almost none of it. Only 'offset' is obliquely explained via the paging caveat; limit, sport, market, event_id, and especially fresh_only (whose interaction with 'stored' odds is exactly what an agent needs to know) are never mentioned.

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 states a specific verb and resource ('Read stored DraftKings-via-ESPN odds') and the word 'stored' implicitly contrasts with live/updated odds siblings. It does not name any sibling or further narrow the resource (event-scoped vs. bulk), so the agent must infer differentiation from the sibling list alone.

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?

There is no explicit when-to-use or when-not-to-use guidance, despite a crowded sibling space (get_updated_odds, get_odds_replay, get_dropping_odds, get_live_events) where routing matters. 'Preserve capture time and source identifiers' is guidance about handling results, not about tool selection.

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.