Skip to main content
Glama

get_events

Read-only

Read stored DraftKings-via-ESPN events. Preserve capture time and source identifiers. Offset pages are not 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_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
sportNo
offsetNo
event_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds a genuinely non-obvious behavioral trait beyond that: 'Offset pages are not a frozen snapshot,' warning that pagination can drift during iteration. It also flags that capture time and source identifiers are meaningful and should be preserved, though it never states ordering, default sort, or result shape.

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?

Three short sentences, front-loaded with the core purpose and no padding. 'Preserve capture time and source identifiers' is syntactically vague — it reads as an instruction rather than a description of the tool's data — which costs a point.

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?

There is no output schema, no parameter documentation at all, and the description never says what an event record contains or how the four filters combine. For a four-parameter listing tool with zero schema description coverage, the definition is markedly under-specified.

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 must carry the burden for four parameters and largely does not. It clarifies only that 'offset' drives non-snapshot paging; limit, sport, and event_id are left to bare type/enum/min-max constraints with no stated meaning or interaction.

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 verb and resource are clear ('Read stored ... events') and the data source ('DraftKings-via-ESPN') is named. However, 'stored' does not distinguish this tool from the sibling get_historical_events or get_live_events, so an agent cannot confidently pick this one from the name and sentence alone.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no 'when not to use', and no named alternative such as get_live_events, search_events, or get_historical_events. The agent is left to infer that 'stored' events are the non-live, non-search path.

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.