Skip to main content
Glama

get_event_state

Read-only

Read verified ESPN event pre/in/post state for a retained DraftKings event. Not settlement verification; receipt time is not provider update time.

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": {
      "event_id": "<event_id>"
    },
    "name": "get_event_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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=true, so safety is covered. The description adds real value beyond that by disclosing two non-obvious semantic caveats: the state is "verified" ESPN data on a "retained" event, and receipt time is explicitly not provider update time, which warns the agent about staleness. It does not describe the returned shape, which keeps it short of a 5.

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?

Two short sentences, front-loaded with the resource and followed by the two constraints. No filler, though the second sentence is compressed to the point of near-telegraphic phrasing.

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?

With no output schema, the description owes the agent some sense of what a "state" payload contains, and it does not provide one. The caveats about settlement and receipt time are the right kind of information, but a caller still cannot tell what fields to expect or how to source a valid event_id.

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?

There is one required parameter with 0% schema description coverage; the schema supplies only a regex pattern (espn-draftkings:espn:LEAGUE:id). The description mentions "retained DraftKings event" but never explains how event_id is formed, where to obtain one, or what makes an event "retained," so it does not compensate for the coverage gap.

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 present ("Read verified ESPN event pre/in/post state") and the scope is qualified ("retained DraftKings event"), which separates it from a plain metadata read like get_event. However, jargon such as "retained" and "pre/in/post state" is left undefined, so an agent cannot confidently predict what a successful response contains.

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?

"Not settlement verification" is a genuine when-not signal and usefully rules out a downstream use. There is no positive when-to-use framing and no named alternative for settlement or odds lookups, so routing against the many sibling get_* tools is left to inference.

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.