Skip to main content
Glama
Sign In
zen-browser

zen-browser

by grapedjuice
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

read_console_messages

Read console logs, warnings, errors, and uncaught exceptions from a browser tab to debug page issues, with filters for patterns, error-only output, limits, and buffer clearing.

Instructions

Read console output (log/info/warn/error/debug and uncaught errors) captured from the tab.

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

Input Schema

NameRequiredDescriptionDefault
clearNoClear the buffer after reading.
limitNo
tabIdNoTab to act on. Defaults to the active tab of the focused Zen window.
patternNoSubstring filter.
onlyErrorsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it only names the log levels. It does not disclose that the output comes from a captured buffer that may reset on navigation, that the clear parameter destroys previously captured messages, or whether results are bounded by a default limit.

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?

A single front-loaded sentence with no filler; every clause contributes. Its brevity is efficient, though it edges into under-specification for a five-parameter tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With five parameters, no annotations, and no output schema, the description should explain what a result set looks like and how the buffer behaves, but it does neither. An agent can identify the tool's domain yet lacks the context to call it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 60%: clear, tabId, and pattern are documented in the schema while limit and onlyErrors are not. The description adds no clarifying detail for any parameter and does not compensate for the undocumented limit or onlyErrors semantics, leaving the reader to guess default page sizes and filter behavior.

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?

"Read console output ... captured from the tab" gives a specific verb and resource, and the parenthetical enumerates the captured levels (log/info/warn/error/debug plus uncaught errors), which singles it out from siblings like read_network_requests. It stops short of explicitly naming a sibling, so it lands at 4 rather than 5.

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 statement of when to reach for this tool versus read_network_requests, javascript, or read_page, and no mention of prerequisites such as a selected tab. The purpose implies a debugging scenario, but the agent must infer it.

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