Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

chrome_console

Capture and retrieve console output from the active browser tab, including earlier messages and uncaught exceptions, to debug page issues.

Instructions

Capture and retrieve all console output from the current active browser tab/page. This captures console messages that existed before the tool was called.

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": {
      "envId": "<envId>"
    },
    "name": "chrome_console"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoURL to navigate to and capture console from. If not provided, uses the current active tab
envIdYesEnvironment ID for the browser environment to operate.
maxMessagesNoMaximum number of console messages to capture (default: 100)
includeExceptionsNoInclude uncaught exceptions in the output (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose one genuinely useful trait: it captures console messages that existed before the call, so the agent knows it is not a live-only stream. It does not say whether the buffer is drained/cleared after retrieval, whether it is a safe read-only operation, or whether capture begins implicitly. Those omissions matter for a tool an agent may call repeatedly.

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?

Two short sentences with zero filler. The primary capability is front-loaded, and the second sentence adds a non-obvious fact rather than restating the name.

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?

For a 4-parameter tool with no annotations and no output schema, the description covers the core action and the pre-existing-message behavior but leaves the return shape (message fields, ordering, truncation at maxMessages) and buffer semantics unexplained. It is adequate to select the tool but thin on what the agent will actually get back.

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 url, envId, maxMessages, and includeExceptions are already documented with defaults. The description adds no parameter meaning at all, and its 'current active tab' wording arguably undercuts the url parameter's navigate-and-capture behavior. Baseline 3 applies when the schema does the heavy lifting.

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: capture and retrieve console output from the active browser tab. That clearly separates it from siblings like chrome_network_capture_start or chrome_get_web_content. It loses a point because it frames the tool as operating only on the 'current active tab/page' while the schema allows navigating to an arbitrary url, leaving the actual scope slightly ambiguous.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no named alternative. An agent must infer on its own that this is the console-log tool versus the network-capture or DOM-content siblings. Only the implicit cue 'console output' points at the right use case.

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