Skip to main content
Glama

ie_console

Retrieve and filter collected page records—script errors, dialogs, console output, and XHR—from instrumented IE mode pages, using since_id to read only new entries.

Instructions

Records the server's page instrumentation made: script errors (kind error), alert/confirm/prompt (dialog-open when it opens, dialog when it closed, with the result), showModalDialog calls (modal: URL, features, dialogArguments, return value), window.open (open), console output (console, only where the page has a console, or all of it with IE_CONSOLE_STUB=1) and native XHR on https pages (xhr). Returns JSON {records, next_since_id}; pass next_since_id as since_id to read only what is new. Optional kinds (a list) and limit (default 100). Records are collected after each tool call, and only from pages the server has instrumented: load-time errors of the first page are not captured, and a dialog that closes between two calls leaves no record. The text is redacted. IE_INSTRUMENT=0 turns all of this off.

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

Input Schema

NameRequiredDescriptionDefault
kindsNoerror, dialog-open, dialog, modal, open, console, xhr
limitNoat most this many, oldest first (default 100)
since_idNoonly records with a higher id (default 0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses capture timing ('collected after each tool call'), coverage gaps, redaction, console availability conditions, and the IE_INSTRUMENT=0 global toggle. It does not explicitly state that the tool is read-only or describe permissions, but it is substantially transparent.

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?

The description is a dense but front-loaded paragraph; every sentence conveys useful information (event types, return shape, pagination, capture limitations, env vars). Slightly long as a single block, but no obvious filler.

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?

Given no output schema and three parameters, the description covers the return shape ({records, next_since_id}), pagination, filtering, capture timing, and important limitations. It does not detail the structure of individual record objects, but is otherwise complete for correct invocation.

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

Parameters4/5

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

Schema coverage is 100%, but the description adds meaningful semantics: it explains that kinds filters record types, limit returns oldest first (default 100), and crucially that since_id should be set to the previous call's next_since_id to read only new records — a pagination pattern not captured in the schema alone.

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 clearly states the tool records/retrieves page instrumentation events and enumerates the event kinds (errors, dialogs, modal, window.open, console, xhr). It is easy to distinguish from ie_console_clear, though the description never names the 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?

The description provides useful context about when records are collected and known gaps (first-page load errors, dialogs closing between calls), but it does not explicitly say when to use this tool versus alternatives like ie_dialog or ie_console_clear.

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