Skip to main content
Glama

get_historical_events

Read-only

Read retained scheduled events in [from,to), a maximum 31-day interval ending no later than now. UTC Z timestamps required. Completion state is unknown; not a complete finished-event archive. 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": {
      "league": "<league>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "get_historical_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
fromYes
limitNo
leagueYes
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Beyond the readOnly/non-destructive annotations, the description discloses non-obvious behavior: offset pages are not a frozen snapshot (pagination is unstable across calls), completion state of events is unknown, data is only DraftKings-via-ESPN, and the interval must not extend past now. These are exactly the traits an agent needs to avoid misinterpreting results, and none are derivable from annotations or schema.

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?

Five terse fragments, front-loaded with the read verb and interval rule, each carrying distinct information with no filler. The telegraphic style costs a little readability but not correctness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only, 5-parameter tool with no output schema, it covers the critical unknowns: data provenance, interval limits, timestamp format, and pagination instability. Remaining gaps are minor – no indication of what an event record contains or how limit interacts with offset.

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%, so the description must carry parameter meaning. It adds real value for from/to (half-open interval, 31-day cap, UTC Z format, end ≤ now) and hints at offset via the snapshot caveat, but limit and league are never explained, and offset's instability is noted without saying how to page safely.

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 retained scheduled events in [from,to)" gives a specific verb plus resource and immediately scopes it to a time interval, so an agent knows this is a retained-events lister rather than a live feed. It does not name sibling alternatives like search_historical_events or get_events, so differentiation relies on the agent's own inference.

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?

It states hard operating constraints (max 31-day interval, must end no later than now, UTC Z required) and a negative caveat ("not a complete finished-event archive"), which tells the agent when results are untrustworthy. However, no alternative tool is named for broader searches or complete archives, so the agent must guess the correct substitute.

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.