Skip to main content
Glama

console_messages

Read-only

Read console output and uncaught errors from a shared browser tab since sharing began, with optional level filtering and clearing.

Instructions

Read console output and uncaught errors from a shared tab since it was shared.

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

Input Schema

NameRequiredDescriptionDefault
tabNoTab handle from list_tabs, e.g. "chrome:812". Optional when only one tab is shared.
clearNo
levelNolog, info, warning, error, debug.
limitNoDefault 100.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read. The description adds real value with the 'since it was shared' accumulation window and the fact that uncaught errors are included, but it is silent on whether the log buffer is cumulative across calls, whether reads consume/clear entries, and what the returned entries look like.

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 no filler; the scope constraint comes immediately after the verb+resource statement.

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?

With no output schema, the description does at least characterize the payload as console output plus uncaught errors, and it explains the tab-handle default. The remaining gap is the shape and pagination of results (levels, timestamps, ordering), which is minor for a read-only inspection tool.

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 75%, so most parameters (tab, level, limit) are already documented in the schema. The description adds no parameter-level meaning of its own, and 'clear' is left undocumented in both places, leaving its effect (clear before reading? clear after?) ambiguous.

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 gives a specific verb and resource ('Read console output and uncaught errors') plus a temporal scope ('since it was shared') that separates it from log-adjacent siblings like get_requests or network_requests. It stops short of naming an explicit alternative, but the resource itself is distinctive enough for an agent to pick it correctly.

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: the tool is clearly for inspecting console/error output from a shared tab, but there is no statement of when to prefer it over request-inspection or JS-evaluation siblings, and no prerequisites beyond the passing mention that tab is optional when one tab is shared.

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