Skip to main content
Glama

get_event

Read-only

Read one retained source event by id, or EVENT_NOT_FOUND. IDs are source-specific, not canonical across bookmakers. 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": {
      "id": "<id>"
    },
    "name": "get_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

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 cover read-only/non-destructive/closed-world, so the value here is the added context: a documented EVENT_NOT_FOUND outcome, the fact that ids are source-specific rather than canonical across bookmakers, the provenance (DraftKings via ESPN), and the caveat that offset pages are not a frozen snapshot. That is substantive behavior beyond the annotations, though it does not address auth or rate limits.

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, front-loaded sentences with no filler; the primary purpose and return sentinel come first. The final clause ('Keep capture timestamps; offset pages are not a frozen snapshot') is dense and slightly cryptic out of context, which costs a point.

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?

With no output schema, the description does the job of indicating the return (one retained source event) and the not-found sentinel, plus data-provenance and timestamp caveats. What's missing is only guidance on obtaining a valid id and on choosing this over sibling retrieval tools.

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 coverage is 0% and the schema only constrains `id` with a regex, so the description must carry meaning — and it does, explaining that the id is a source-specific event id from the stored DraftKings/ESPN feed rather than a cross-bookmaker canonical key. It still doesn't clarify where such an id is obtained.

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: 'Read one retained source event by id', plus the failure sentinel EVENT_NOT_FOUND. It also scopes the data ('retained source event', 'Stored DraftKings via ESPN only'), which separates it from a canonical-events lookup, but it never names a sibling like get_events or search_events.

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?

Implicitly the single-record counterpart to listing/search tools, and the 'IDs are source-specific' note implies you must have a source event id in hand first. No explicit when-to-use, when-not, or pointer to an alternative sibling is given.

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.