Skip to main content
Glama

Get Match Events

get_match_events
Read-only

Retrieve paginated play-by-play events for a finished match to support detailed recaps and game analysis; pass nextCursor to load subsequent pages.

Instructions

One page (up to 200) of play-by-play for a finished match. Request is paginated with a cursor, pass nextCursor from the result for the next page. Use it only when the user request it or to get a detailed recap or analysis of a game.

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": {
      "match_id": "<match_id>"
    },
    "name": "get_match_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNo
match_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

readOnlyHint=true already covers the safety profile, so the description's job is to add operational context — and it does: page size ceiling of 200, cursor-based pagination, and the restriction to finished matches (a real eligibility constraint not in the annotations or schema). It doesn't discuss rate limits or ordering of events, keeping it at a solid 4 rather than 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?

Three short sentences with the core payload (what it returns, page size) front-loaded, then pagination, then usage. Minor waste and an ungrammatical clause ('when the user request it') keep it from a 5.

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?

An output schema exists, so return values need no explanation, and for a simple two-parameter read tool the description covers pagination, page limits, and match-state eligibility. The only gap is the cursor/nextCursor naming mismatch, which an agent must reconcile itself.

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% across two parameters, so the description must carry the load. It explains the pagination parameter's semantics but refers to the returned field 'nextCursor' while the actual input parameter is named 'cursor', which can create a mapping ambiguity, and it says nothing about match_id beyond what the name implies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: play-by-play events for a finished match, capped at 200 per page. It also implicitly separates this from the lighter sibling get_match by framing itself as the 'detailed recap or analysis' source, so an agent can tell what it returns without opening the schema.

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

Usage Guidelines4/5

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

Gives an explicit when-to-use rule: only when the user asks for it, or when a detailed recap/analysis is needed. It stops short of naming an alternative tool (e.g. get_match for summary data) or stating an explicit when-not, so routing is implied rather than spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.