Skip to main content
Glama

get_updated_odds

Read-only

Read current offers with retained changes strictly after since, within the last seven days. Not durable replay or complete change history. 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": {
      "since": "<since>"
    },
    "name": "get_updated_odds"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
sinceYes
sportNo
marketNo
offsetNo
fresh_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish read-only, non-destructive, closed-world behavior, so the bar is lower, and the description still adds real context beyond them: a 7-day retention window, a single-source restriction (DraftKings via ESPN), and a consistency caveat that offset pages are not a frozen snapshot. What it leaves undisclosed is the meaning of fresh_only and what an "offer" record actually contains.

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, front-loaded sentences with no filler; the temporal scope and source constraint come first and the caveats follow. The compressed, note-like phrasing borders on cryptic but every sentence contributes a distinct constraint.

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 six-parameter tool with no output schema and no parameter descriptions, the definition covers purpose, time window, source, and pagination caveats but not the return shape or the remaining parameters. An agent could call it correctly at a basic level but would be guessing on filtering and freshness behavior.

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 six parameters, so the description carries the full burden. It clarifies `since` (strictly after, bounded to seven days) and `offset` (paging is not a frozen snapshot), but says nothing about `limit`, `sport`, `market`, or the ambiguous `fresh_only` flag, which is the parameter most likely to be misused.

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 uses a specific verb and resource ("Read current offers with retained changes strictly after since") and scopes it in time ("within the last seven days") and by source ("Stored DraftKings via ESPN only"). It also draws a line against a replay-style sibling with "Not durable replay or complete change history," so the tool is distinguishable, though the phrase "retained changes" and "offers" is telegraphic and an agent must infer it means incremental odds updates.

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

Usage Guidelines4/5

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

It gives a clear when-to-use condition (fetch what changed since a timestamp, within a 7-day window) and an explicit when-not ("Not durable replay or complete change history"), which effectively routes the agent away from a replay sibling. It never names the alternative tool explicitly, so the routing is implied rather than stated.

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.