Skip to main content
Glama
Sign In
chrome

chrome

by wellrccity
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Read console

console

Read browser logs, warnings, errors, and unhandled rejections captured since page load; clear the buffer when you need a fresh capture.

Instructions

Read console logs, warnings, errors and unhandled rejections captured since page load. Use action="clear" to reset the buffer.

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

Input Schema

NameRequiredDescriptionDefault
levelNo
limitNo
tabIdNo
actionNoget

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

B3.2/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 burden, and it does disclose the buffer semantics ("captured since page load") and that clear resets it — useful, non-obvious traits. However, it omits whether a tabId is needed, whether the call is scoped to one tab, and any rate/size behavior (the 200/400 limit caps).

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 tight sentences with zero filler; the core behavior is front-loaded and the clear-buffer hint is a compact, high-value second sentence.

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?

No annotations, no output schema, and 0% schema coverage on a 4-parameter tool means the description should do more. It never explains the return shape (entries, ordering, truncation) or the role of `limit`/`tabId`, leaving an agent unable to invoke 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 description coverage is 0% across 4 parameters, so the description must compensate and largely doesn't. It touches `action` via the clear example and loosely gestures at `level` through the enumerated event types, but `limit` (default 200, max 400) and `tabId` are completely undocumented anywhere.

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+resource (read console logs) and enumerates the captured event types (warnings, errors, unhandled rejections), which makes it distinct from most siblings. It does not explicitly separate itself from near neighbors like `debugger` or `network`, so it falls short of full sibling differentiation.

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?

The description gives one concrete usage instruction: use action="clear" to reset the buffer. It offers no guidance on when to reach for console output versus `debugger`, `network`, or `evaluate`, and no prerequisites (e.g., requires an active tab). Usage is implied rather than framed as a decision.

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