Skip to main content
Glama

get_odds_summary

Read-only

Summarize matching event/market/period/line quotes captured within 15 minutes. One independent bookmaker only, not cross-book consensus. Normalized prices are not verified win probabilities; incomplete or incoherent sides yield null normalization. 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_id": "<event_id>"
    },
    "name": "get_odds_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
marketNo
offsetNo
event_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior5/5

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

Annotations only declare a safe read operation; the description adds material behavior the agent could not otherwise know: a 15-minute capture window, single-bookmaker sourcing, null normalization for incomplete sides, DraftKings-via-ESPN provenance, and the warning that offset pages are not a frozen snapshot. These are exactly the staleness and data-quality caveats needed before trusting the numbers.

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?

Six short sentences, front-loaded with the core action and caveats, with no filler. Some phrasings are telegraphic to the point of opacity ("Stored DraftKings via ESPN only"), which costs a little clarity but not length.

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 tool with no output schema and zero schema description coverage, the caveats are unusually good but the mechanics are thin: nothing describes what the summary contains, how limit/offset paginate, or whether event_id accepts names. Adequate, not complete.

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?

Schema description coverage is 0% across four parameters, so the description must compensate. It does explain offset semantics ("Offset pages are not a frozen snapshot") and implies market filtering, but says nothing about limit, event_id format, or what each market enum value returns. Partial compensation only.

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 verb and resource: "Summarize matching event/market/period/line quotes captured within 15 minutes." It also scopes itself against a plausible sibling behavior ("not cross-book consensus"), though it never names an alternative tool. Terms like "period" and "line" do not map to any schema parameter, leaving the object of the summary slightly ambiguous.

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?

Usage is implied through scope constraints (single bookmaker, 15-minute capture window, DraftKings via ESPN only) rather than stated. There is no explicit "use this when…" or "use get_odds / get_multiple_odds_summaries instead when…" routing, even though several siblings clearly overlap. An agent must infer the selection rule from the caveats.

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.