Skip to main content
Glama

ie_windows

Lists all windows in the current IE session as JSON, including dialog state, targets, and driver handles, so you can identify and target windows or switch pages even while a dialog is open.

Instructions

List the windows of the session as JSON: hwnd, kind (main | popup | html_dialog | script_dialog | system_dialog), class, title, url, owner_hwnd, visible, is_prompt and target ("hwnd:", for the target argument of the other tools). When no modal dialog is open and the browser is free it also gives each page window's driver_handle (for ie_switch_window) and which one is current. Never waits for a busy browser and works while a dialog is open. A system dialog is listed so you can tell the user: it is never answered by these tools.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full behavioral burden and does so well. It discloses non-blocking behavior ('Never waits for a busy browser'), operation while a dialog is open, conditional driver_handle availability, and the important constraint that system dialogs are never answered by these tools.

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?

The description is front-loaded with the core action and then provides the return fields and behavioral caveats. Every sentence contributes either field meaning, usage routing, or a non-obvious behavioral constraint.

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?

There is no output schema and no annotations, so the description must explain both return contents and behavior. It lists the returned fields, explains conditional fields like driver_handle, and clarifies the system-dialog limitation, making it complete for an agent to call correctly.

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 takes no parameters, so there are no parameter semantics to explain. The baseline for a zero-parameter tool is 4, and the description appropriately focuses on output and behavior instead.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: list the windows of the session as JSON. It enumerates the returned fields and window kinds, so the agent can distinguish this enumeration tool from actions like ie_switch_window or ie_dialog.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It tells the agent that the target field is for the target argument of the other tools and that driver_handle is for ie_switch_window. It also explains that a system dialog should be surfaced to the user because these tools never answer it. It stops short of explicit when-not-to-use guidance, but the routing context is clear.

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