Skip to main content
Glama

get_multiple_odds_summaries

Read-only

Same single-book summary contract for 1–20 comma-separated event_ids. Maximum 2,000 input offers; narrow the selection on RESULT_TOO_LARGE. Missing events produce no invented rows. Stored DraftKings via ESPN only. 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_odds_summaries"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
marketNo
offsetNo
event_idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior4/5

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

Beyond the readOnly/non-destructive annotations, it discloses meaningful behavior: the 2,000-offer cap, RESULT_TOO_LARGE handling, that missing events yield no invented rows, the DraftKings-via-ESPN data source, and that offset pages are not a frozen snapshot. These are exactly the operational traits an agent needs, though return shape is left implicit.

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?

Dense and front-loaded, with the key batching constraint first and constraints after; no wasted sentences. It is telegraphic and jargon-heavy, but every sentence carries operational information.

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?

For a 4-param, no-output-schema tool it covers limits, data source, pagination, and missing-data behavior well. It still leaves the limit/market parameters and the actual return content unaddressed, so it is adequate rather than complete.

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%, so the description must carry parameter meaning, yet it only explains event_ids (comma-separated, 1–20). The limit and market parameters are never clarified, and offset is only hinted at via the snapshot caveat, leaving most parameters undocumented in both schema and prose.

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

Purpose3/5

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

It conveys that this fetches odds summaries in bulk for 1–20 event_ids and references a 'single-book summary contract,' so an agent can infer it's the batch analog of get_odds_summary. But the core verb/resource (what a 'summary contract' returns) is jargon rather than a plain statement, and no sibling is named, leaving the purpose understandable but not crisp.

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?

'narrow the selection on RESULT_TOO_LARGE' and the 1–20 id bound give practical guidance on how to call it correctly. However, it never states when to prefer this over get_odds_summary or get_multiple_event_odds, so alternative selection is left to inference.

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.