Skip to main content
Glama
Triggered0

lcu-mcp

by Triggered0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Drain buffered LCU events

lol_events_poll
Read-onlyIdempotent

Poll buffered League Client WebSocket events since a sequence cursor to incrementally consume live client updates after recording starts, returning new events and the next cursor.

Instructions

Drain buffered League Client WebSocket events recorded since a given sequence cursor, returning events and the new cursor. Use this tool to incrementally consume live client events after calling lol_events_start. For recording full WAMP traffic frames, use lol_wamp_record_dump instead. If an event payload indicates truncated: true, use lol_get on the entry URI to fetch the full resource. Behavior: Safe and read-only. A non-zero dropped count indicates buffer overflow between polls.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of event entries to return (1-500, default: 100)
sinceNoMonotonic sequence cursor from the previous poll call; omit or set to 0 to read from start of buffer
filterNoOptional case-insensitive URI prefix substring applied as a post-filter at poll time

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.6.0
    • changedInput schema / properties / filter / description
      Previous value: -"extra URI prefix applied at poll time"New value: +"Optional case-insensitive URI prefix substring applied as a post-filter at poll time"
    • changedInput schema / properties / limit / description
      Previous value: -"max entries to return, default 100"New value: +"Maximum number of event entries to return (1-500, default: 100)"
    • changedInput schema / properties / since / description
      Previous value: -"cursor from the previous poll; omit to start at 0"New value: +"Monotonic sequence cursor from the previous poll call; omit or set to 0 to read from start of buffer"
  2. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare read-only/idempotent/destructive=false, and the description adds real context on top: truncated-payload fallback via lol_get, and the meaning of a non-zero dropped count as buffer overflow between polls. That's behavioral insight the structured fields do not carry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action and return, followed by usage routing, fallback behavior, and safety note. Every sentence carries distinct, non-redundant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, yet the description explains the return (events and the new cursor), the dropped-count signal, and the truncation follow-up path. Nothing essential for correct invocation is missing.

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 100%, so the schema already documents all three parameters; the description reinforces the 'since' cursor as a cursor from the previous poll and ties limit/filter semantics into the poll flow. It adds meaningful framing beyond the schema, though it doesn't detail filter syntax.

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 ('Drain buffered League Client WebSocket events') plus return semantics (events + new cursor). It distinguishes itself from lol_events_start and lol_wamp_record_dump, so an agent can identify it without opening any schema.

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

Usage Guidelines5/5

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

Explicitly says to use it 'to incrementally consume live client events after calling lol_events_start' and names the alternative for full frames (lol_wamp_record_dump). When-to-use, sequencing, and alternatives are all covered.

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

Deploy Server

Other Tools