Skip to main content
Glama

ie_status

Reports the current IE Mode browser session state, including page/window details, instrumentation, network capture, and active modifications; flags a busy driver without waiting.

Instructions

Session state as JSON: active/alive, title, url, window_handles, and the interaction mode, session identity/directory, owned browser PIDs/profile, the page modifications: instrumented (wrappers installed), console_stub, xhr_wrapped, and the network capture: capture (proxy, page-only, off, unverified), capture_note (what it does not show), capture_internal_errors (proxy bugs, if any) and modifications (every active change the harness makes to pages, requests and input, each with its off switch). Never waits for a busy browser: while another call holds it, title/url/window_handles are left out and "driver": "busy" is reported.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well for a status tool: it enumerates returned fields, explains session identity and capture internals, and discloses the busy-browser behavior where title/url/window_handles are omitted and driver is 'busy'. It does not explicitly state that the tool is read-only, but the status semantics strongly imply no mutation.

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 front-loaded with 'Session state as JSON' and every listed field earns its place because there is no output schema. The first sentence is dense and run-on, but the information is relevant and not padded with generic filler.

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

Completeness5/5

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

Given zero parameters, no annotations, and no output schema, the description provides a thorough account of the return payload and a key concurrency behavior. It is complete enough for an agent to know what calling ie_status will yield and how a busy browser affects the response.

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?

The tool has zero parameters, so there is no parameter semantics to clarify beyond confirming no input is required. The baseline for a zero-parameter tool is 4.

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 opens by stating exactly what the tool returns: session state as JSON, followed by a detailed inventory of fields. It is clear it is a read-oriented status/introspection tool, but it does not explicitly differentiate itself from siblings such as ie_browsers or ie_tabs.

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 implied: inspect session state, especially page modification and network capture state. However, the description gives no explicit when-to-use guidance, no when-not-to-use conditions, and no named alternatives for related status checks.

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