Skip to main content
Glama

search_events

Read-only

Search retained home/away team names by literal case-insensitive text. May include past scheduled events. Stored DraftKings via ESPN only. Keep capture timestamps; 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": {
      "q": "<q>"
    },
    "name": "search_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYes
limitNo
sportNo
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the read-only, non-destructive, closed-world profile, and the description adds real context beyond them: the data source is limited to DraftKings-via-ESPN, matching is literal and case-insensitive, results may include past scheduled events, and offset pages are not a frozen snapshot so capture timestamps must be retained.

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, purpose front-loaded, with the operational caveats (source restriction, timestamp retention) following. Some phrasing is telegraphic ('Stored DraftKings via ESPN only') but no sentence is wasted.

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?

Covers matching behavior, data provenance, historical inclusion, and pagination instability, which is good for a search tool with no output schema. However, it never characterizes the result shape (beyond team names) or the effect of limit/sport, leaving gaps an agent must discover by calling.

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% for four parameters, so the description must compensate and only partially does. It clarifies matching semantics for 'q' and warns that 'offset' paging is unstable, but says nothing about 'limit' or how 'sport' constrains results.

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?

States a specific verb and resource: searching retained home/away team names by literal case-insensitive text, with the added scope that past scheduled events may be included. It is distinguishable from a generic event lookup, though it never names the sibling (search_historical_events) that presumably narrows to history.

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?

Usage is implied rather than stated: 'literal case-insensitive text' tells the agent this is substring matching, not fuzzy or semantic search, and 'may include past scheduled events' hints at overlap with the historical search sibling. There is no explicit when-to-use / when-not / use-X-instead routing.

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.