Skip to main content
Glama
Triggered0

lcu-mcp

by Triggered0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Read buffered client console output

lol_cdp_console_tail
Read-onlyIdempotent

Retrieve buffered browser console logs, warnings, and JavaScript exceptions for debugging frontend errors, component mounting, or UI scripts; call console start first.

Instructions

Retrieve buffered console logs, warnings, and runtime JavaScript exceptions recorded since the tailer was started or past a given cursor. Use this tool to inspect frontend errors, check component mounting logs, or debug UI scripts. Prerequisite: Must call lol_cdp_console_start first; fails if tailer is not running. For HTTP request traffic, use lol_cdp_network_tail instead. Behavior: Sequential integer cursors ensure gap-free incremental reading without skipping entries.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textNoCase-insensitive substring filter matching log message text
levelNoFilter by console severity level, e.g. "error", "warning", "info", or "log"
limitNoMaximum number of entries to return (1-2000, default: 100)
sinceNoLower timestamp bound in epoch milliseconds; excludes older entries
untilNoUpper timestamp bound in epoch milliseconds; excludes newer entries
cursorNoSequence cursor from a previous tail call for incremental polling
targetIdNoFilter entries to a specific CDP renderer target ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.6.0
    • changedInput schema / properties / cursor / description
      Previous value: -"seq cursor from a previous tail"New value: +"Sequence cursor from a previous tail call for incremental polling"
    • changedInput schema / properties / level / description
      Previous value: -"console severity, e.g. \"error\" or \"warning\""New value: +"Filter by console severity level, e.g. \"error\", \"warning\", \"info\", or \"log\""
    • changedInput schema / properties / limit / description
      Previous value: -"max entries, default 100"New value: +"Maximum number of 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; excludes older entries"
    • changedInput schema / properties / targetId / description
      Previous value: -"restrict to one renderer incarnation"New value: +"Filter entries to a specific CDP renderer target ID"
    • changedInput schema / properties / text / description
      Previous value: -"case-insensitive substring of the message"New value: +"Case-insensitive substring filter matching log message text"
    • changedInput schema / properties / until / description
      Previous value: -"upper bound on ts, epoch milliseconds"New value: +"Upper timestamp bound in epoch milliseconds; excludes newer entries"
  2. Addedv0.2.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world. Beyond that, the description discloses the failure mode (errors when tailer isn't running), the prerequisite chain, and gap-free cursor polling semantics - behavioral context not present in the annotations.

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?

Front-loaded purpose followed by use cases, prerequisite, alternative, and cursor behavior - each sentence earns its place with no filler. Slightly dense but well ordered.

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?

For a 7-param read tool with no output schema, the description covers what is returned (logs, warnings, exceptions), the prerequisite, and incremental polling semantics. Return-shape specifics (fields per entry) remain implicit, but annotations carry the safety profile.

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 100%, so the schema already documents all 7 parameters including cursor. The description only adds the conceptual framing of cursors as sequential gap-free markers, without syntax or format detail beyond what the schema provides; baseline 3 applies.

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 (retrieve buffered console logs, warnings, JS exceptions) with scope boundaries (since tailer started or past a cursor). It explicitly carves out the sibling lol_cdp_network_tail for HTTP traffic, so an agent can distinguish them without opening schemas.

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?

Names concrete use cases (inspect frontend errors, check mounting logs, debug UI scripts), states a hard prerequisite (must call lol_cdp_console_start first; fails if tailer not running), and routes HTTP traffic to an alternative tool.

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