Skip to main content
Glama

get_history

Read-only

Read stored DraftKings-via-ESPN history. Requires event_id or offer_id; retained changes kept since November 2026.

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_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
sportNo
marketNo
offsetNo
event_idNo
offer_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already establish the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the lower bar applies. The description adds useful context the annotations do not carry: the upstream source (DraftKings via ESPN) and a retention boundary ("retained changes kept since November 2026"). It still says nothing about ordering, pagination behavior, or whether a missing record is an empty result or an error.

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?

Two short sentences with no filler, and the hard precondition is placed immediately after the purpose statement. "Retained changes kept since November 2026" is slightly awkward phrasing but still earns its space as a data-freshness caveat.

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?

This is a six-parameter tool with no output schema and no parameter descriptions, so the description is the only place return shape and pagination could be explained, and it says nothing about either. Given the enumerated sport and market filters and the offset/limit pair, an agent cannot tell what a result record looks like or how to page through a large history. The retention note and ID requirement are helpful but do not close that gap.

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 carries the full burden, and it covers only the event_id/offer_id pair. Crucially, it asserts a one-of constraint ("Requires event_id or offer_id") that the schema's empty required list does not express, which is valuable but unconfirmed. The other four parameters (limit, offset, sport, market) get no semantic treatment at all; their enums are partially self-documenting but limit/offset pagination semantics remain entirely undocumented.

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?

The description states a specific verb and resource ("Read stored DraftKings-via-ESPN history"), which narrows the scope to one book/source. However, "history" is underspecified in a catalog full of history-adjacent siblings (get_odds_replay, get_historical_events, get_prop_history, get_prediction_market_history), and the description does nothing to distinguish this tool from them. An agent can guess it returns past odds data but cannot confidently separate it from the alternatives on description text alone.

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?

"Requires event_id or offer_id" gives a real precondition that effectively gates invocation, which is genuine usage guidance. What is missing is any when-to-use vs when-not signal, especially against get_odds_replay or get_prop_history, and no hint about what to do when neither ID is known (e.g., whether search_events should be called first).

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.