Skip to main content
Glama

inspect_console

Capture and filter browser console output to diagnose JavaScript errors, warnings, uncaught exceptions, and messages during web inspection.

Instructions

Capture and inspect browser console output: JavaScript errors, warnings, uncaught exceptions, and console messages.

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": "inspect_console"
  }
}

Input Schema

NameRequiredDescriptionDefault
clearNoClear console history after reading (default: false)
levelNoFilter logs by level: "all", "error", "warn", or "info" (default: "all")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations present, the description must carry the full behavior burden. It usefully discloses which message categories are captured (errors, warnings, uncaught exceptions, console messages), which implies a persistent buffer, but it never says whether the page must be loaded, whether output is a snapshot vs. streaming, or what clears or persists history.

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?

A single front-loaded sentence with zero redundant wording; the resource and captured content types are stated before any qualifiers.

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 simple two-parameter read tool with no output schema, the description covers what is captured but omits key context an agent needs before calling: whether a page must be open, whether history spans navigations, and roughly what the returned payload looks like beyond a list of categories.

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% and both parameters (clear, level) have descriptive text with defaults and enum values spelled out in the schema. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

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?

"Capture and inspect browser console output" states a concrete verb and resource, and the enumeration (JavaScript errors, warnings, uncaught exceptions, console messages) makes the scope unambiguous. The resource itself (console) naturally separates it from inspect_network, inspect_styles, or inspect_element, though the description never names any sibling explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the tool for debugging JavaScript errors or checking console-side messages. There is no statement of when to prefer it over inspect_network or inspect_page, and no preconditions (e.g., a page must be open) are given.

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