Skip to main content
Glama

get_live_events

Read-only

Read native FanDuel events with in-play market observations in the past15 minutes. Observation evidence only, not current-state assurance; no inferred completion. Does not require price selection.

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_live_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNo
limitNo
sportNo
leagueNo
event_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely new behavioral context beyond them: the 15-minute freshness window, the warning that results are 'observation evidence only, not current-state assurance', and that no completion is inferred. It still says nothing about ordering, pagination, or result shape, which is a real gap for a 5-param listing tool.

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 resource and window, with no filler. The 'past15 minutes' typo and the slightly cryptic final clause cost it a point but do not impede comprehension.

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?

The staleness caveat is the right kind of content for a live-data tool with no output schema, and annotations carry the safety profile. However, with five undocumented parameters and no output schema, the definition leaves an agent unable to tell how to scope, paginate, or size the query.

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% across five parameters (after, limit, sport, league, event_id), and the description compensates for none of them; it never mentions filtering, the cursor, or the default/maximum limit. The only parameter-adjacent remark, 'does not require price selection', does not correspond to any declared input.

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: reading native FanDuel events with in-play market observations over a bounded 15-minute window, which is far more informative than the bare name. It never names a sibling such as get_events or get_fanduel_markets to sharpen the distinction, 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?

Usage is only implied: the 'past15 minutes' window and the 'does not require price selection' note gesture at a live-observation use case versus price-oriented or historical tools, but no alternative is named and no explicit when-to-use or when-not-to-use rule 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.