Skip to main content
Glama

search_historical_events

Read-only

Search retained scheduled events by literal team-name text in [from,to), at most 31 days and no future end. UTC Z timestamps required. Completion is not verified. 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>",
      "q": "<q>"
    },
    "name": "search_historical_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYes
toYes
fromYes
limitNo
leagueYes
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds non-obvious behavioral details: 'Completion is not verified' (data-quality caveat), 'Stored DraftKings via ESPN only' (source coverage), and 'Offset pages are not a frozen snapshot' (pagination consistency warning). These are meaningful traits beyond annotations, though 'completion' is somewhat ambiguous.

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?

The description is dense and front-loaded: purpose first, then time-range constraints, data-quality caveat, source coverage, and pagination warning. Every sentence carries information, though the telegraphic style ('Completion is not verified') is slightly opaque and could be clearer without adding length.

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 six-parameter search tool with no output schema, the description covers purpose, source provenance, time-range rules, timestamp format, data-completeness caveat, and pagination behavior. It omits return shape and sort order, but for a read-only search endpoint with annotations covering safety, it is largely complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 explains q as 'literal team-name text' rather than general text, specifies UTC Z timestamp format for from/to, states the [from,to) half-open interval, imposes a 31-day maximum and no-future-end rule, and clarifies offset pagination instability. It does not explain limit semantics, but the schema provides defaults and bounds.

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 states a specific verb and resource: 'Search retained scheduled events by literal team-name text in [from,to)'. It clarifies the search is literal team-name based and limited to retained/stored events, which distinguishes it from a generic event search. It does not explicitly name a sibling alternative, so it stops short of 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?

Constraints imply when the tool is usable: at most 31 days, no future end, UTC Z timestamps, and only DraftKings-via-ESPN data. However, it never explicitly says when to use this tool versus siblings like get_historical_events or search_events. The guidance is implied by constraints rather than stated as a routing 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.