Skip to main content
Glama

get_odds_replay

Read-only

Read one bounded retained odds-change page. Preserve decimal-string next_after and through until catch-up completes. Seven-day retention; expired anchors require deliberate resync. Not streaming, complete capture, deletion events, or 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_replay"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNo0
limitNo
sportNo
marketNo
throughNo
event_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior5/5

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

Annotations already establish readOnly/non-destructive/closed-world, and the description adds substantial context beyond them: a seven-day retention window, the fact that expired anchors require a deliberate resync, and an explicit list of what the data is NOT (streaming, complete capture, no deletion events, no frozen snapshot). These are exactly the behavioral limits an agent cannot infer from the annotations or schema. The only quibble is the reference to "next_after," which does not appear in the input schema and may be a response field with no output schema to document it.

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 the core action and followed by paging rules, retention, and exclusions. There is no filler, though the compressed telegraphic style ("Not streaming, complete capture, deletion events...") costs a little readability and the undefined "next_after" adds mild confusion.

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?

The description is strong on data semantics and retention but thin on the mechanics an agent needs to actually call it: filtering by sport/market/event_ids, page size limits, and what a page contains are unaddressed, and with no output schema the return shape is undocumented. For a six-parameter paginated read tool, this leaves notable gaps. It is adequate but incomplete.

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 and largely fails it. It mentions "through" and a "next_after" value that is not even an input parameter, while leaving after, limit, sport, market, and event_ids completely unexplained. The one useful hint is that cursors are decimal strings that must be preserved verbatim, but that does not cover the parameter set.

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?

"Read one bounded retained odds-change page" gives a specific verb (read), a specific resource (retained odds-change records), and a scope (one bounded page). The trailing negation list further narrows the resource by ruling out streaming, complete capture, deletion events, and frozen-snapshot semantics, which meaningfully separates it from snapshot-style siblings like get_odds. It stops short of naming a concrete alternative, so it is not a 5.

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?

"Preserve decimal-string next_after and through until catch-up completes" and "expired anchors require deliberate resync" give real operational guidance for paging through catch-up, including what to do when an anchor has expired. However, there is no statement of when to choose this tool over the many sibling odds tools, which is the core of this dimension. Guidance is implied by the catch-up/replay framing rather than stated as a selection rule.

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.