Skip to main content
Glama
Triggered0

lcu-mcp

by Triggered0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Dump the recorded WAMP timeline

lol_wamp_record_dump
Read-onlyIdempotent

Dumps recorded WAMP timeline entries, WebSocket lifecycle events, and per-URI statistics so you can inspect frames and tell whether a quiet URI had no traffic or its socket disconnected.

Instructions

Retrieve recorded WAMP timeline entries, socket lifecycle events, and cumulative per-URI statistics from the recorder buffer. Use this tool to inspect recorded WebSocket frames and diagnose whether a quiet URI received no traffic or the socket disconnected. Prerequisite: lol_wamp_record_start must have been called. For general timeline correlation across multiple subsystems, use lol_forensics_correlate. Behavior: Returns timestamped entries, dropped frame count, and cumulative per-URI stats surviving eviction.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uriNoFilter event entries by URI prefix; lifecycle events survive this filter
kindsNoFilter entries strictly to specified event kinds (e.g. ["event", "open", "close", "error", "reconnect"])
limitNoMaximum entries to return (1-2000, default: 100)
sinceNoLower timestamp bound in epoch milliseconds
untilNoUpper timestamp bound in epoch milliseconds
cursorNoSequence cursor from a previous dump call for incremental pagination

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.6.0
    • changedInput schema / properties / cursor / description
      Previous value: -"seq cursor from a previous dump"New value: +"Sequence cursor from a previous dump call for incremental pagination"
    • changedInput schema / properties / kinds / description
      Previous value: -"restrict to these entry kinds"New value: +"Filter entries strictly to specified event kinds (e.g. [\"event\", \"open\", \"close\", \"error\", \"reconnect\"])"
    • changedInput schema / properties / limit / description
      Previous value: -"max entries, default 100"New value: +"Maximum entries to return (1-2000, default: 100)"
    • changedInput schema / properties / since / description
      Previous value: -"lower bound on ts, epoch milliseconds"New value: +"Lower timestamp bound in epoch milliseconds"
    • changedInput schema / properties / until / description
      Previous value: -"upper bound on ts, epoch milliseconds"New value: +"Upper timestamp bound in epoch milliseconds"
    • changedInput schema / properties / uri / description
      Previous value: -"URI prefix filter, applied to event entries only"New value: +"Filter event entries by URI prefix; lifecycle events survive this filter"
  2. Addedv0.2.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior, but the description adds substantial context beyond that: it discloses the returned data shape (timestamped entries, dropped frame count, cumulative stats surviving eviction), the prerequisite, and the diagnostic purpose. No behavioral traits are contradicted.

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?

The description is front-loaded with the core purpose, followed by usage context, prerequisite, alternative, and behavior. Every sentence contributes useful information without redundancy or filler.

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?

Given six optional parameters, full schema descriptions, a meaningful annotation set, and no output schema, the description supplies the necessary context: what it returns, when to use it, the prerequisite, and an alternative tool. Nothing an agent needs to invoke it correctly is missing.

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 coverage is 100%, so all six parameters are fully documented in the input schema with descriptions, enums, ranges, and pagination semantics. The description adds no parameter-specific syntax or meaning beyond what the schema already provides, so the baseline score of 3 is appropriate.

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?

The description states a specific verb and resource ('Retrieve recorded WAMP timeline entries, socket lifecycle events, and cumulative per-URI statistics') and clearly distinguishes this from sibling tools by naming an explicit alternative for broader correlation. An agent can identify the tool's scope 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 Guidelines5/5

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

It states when to use the tool ('inspect recorded WebSocket frames and diagnose whether a quiet URI received no traffic or the socket disconnected'), gives the prerequisite ('lol_wamp_record_start must have been called'), and names an explicit alternative for a different use case ('For general timeline correlation across multiple subsystems, use lol_forensics_correlate').

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