Skip to main content
Glama

Read buffered browser diagnostics

browser_debug

Retrieve buffered console errors, uncaught page errors, and failed network requests since browser launch to diagnose rendering issues or unexplained action failures.

Instructions

Return buffered console errors, uncaught page errors and failed network requests collected since the browser started. Use this when a page renders incorrectly or an action fails for an unknown reason.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "browser_debug"
  }
}

Input Schema

NameRequiredDescriptionDefault
clearNoClear the buffer after reading it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden. It does establish the key behavior that output is buffered and cumulative since browser start, which matters, but it says nothing about whether the buffer is bounded or evicts entries, whether it is per-page or global, or that reading is read-only and safe to repeat.

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 sentences, zero filler, with the content of the return value front-loaded before the usage trigger. Nothing is repeated or padded.

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 one-optional-parameter read tool this is nearly sufficient; the enumerated categories describe what comes back even without an output schema. The remaining gap is the shape of each record (message text, URL, status) and whether the call is safe to invoke repeatedly.

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% and the single optional 'clear' parameter is fully described in the schema itself, so the description needs only to avoid contradicting it. It adds no extra meaning about the buffer-clearing side effect, but the baseline of 3 applies when the schema does the work.

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?

The description uses a specific verb ('Return') plus an enumerated resource: buffered console errors, uncaught page errors, and failed network requests, scoped to 'since the browser started'. That scope phrase separates it from a live-log or snapshot tool, though no sibling is named explicitly.

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?

It gives clear triggering conditions: 'when a page renders incorrectly or an action fails for an unknown reason.' What is missing is the negative case and any pointer to an alternative when the failure cause is known or when a structural view (e.g. a snapshot) is wanted.

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