Skip to main content
Glama

get_multiple_event_odds

Read-only

Read a combined page of stored offers for up to 20 distinct comma-separated event_ids. Missing events are not invented. Stored DraftKings via ESPN only. Keep capture timestamps; offset pages are not a frozen snapshot.

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": {
      "event_ids": "<event_ids>"
    },
    "name": "get_multiple_event_odds"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
sportNo
marketNo
offsetNo
event_idsYes
fresh_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already cover read-only and closed-world safety, and the description adds genuinely new behavioral facts: missing events are not fabricated, coverage is limited to stored DraftKings via ESPN, and offset pages are not a frozen snapshot (so results can shift between pages). It stops short of stating rate limits or how missing events are signalled in the response.

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?

Four short sentences, front-loaded with purpose before the data-source and pagination caveats. The telegraphic phrasing ('Stored DraftKings via ESPN only') is efficient but verges on cryptic.

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 tool with zero schema coverage and no output schema, the description omits far too much: the meaning of limit/offset/sport/market/fresh_only, and what the combined page actually contains. What remains (max 20 ids, no fabrication, unstable pagination) is useful but does not make the definition self-sufficient.

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

Parameters2/5

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

Schema description coverage is 0% across 6 parameters, so the description carries the full burden, yet it only explains event_ids (comma-separated, max 20). limit, offset, sport, market, and fresh_only are left entirely unexplained, and 'Keep capture timestamps' is too terse to clarify the pagination or freshness semantics.

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 a specific verb and resource ('Read a combined page of stored offers') and scopes it to 'up to 20 distinct comma-separated event_ids', which is concrete enough to distinguish it from single-event tools. It never explicitly contrasts itself with the closest sibling get_multiple_odds_summaries, so the differentiation is only implicit.

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

Usage Guidelines3/5

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

'Stored' plus 'Stored DraftKings via ESPN only' implies this is for cached DraftKings/ESPN pricing rather than live or multi-book data, which gives an agent a rough sense of when to pick it. There is no explicit when-to-use or when-not-to-use statement, and no named alternative for live odds or other bookmakers.

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.