Skip to main content
Glama

ie_attach

Attach to a chosen IE-mode tab so read and interact tools act on it without a target. Preserves the user's login and page state while enabling COM-based control.

Instructions

Attach to one of the user's IE-mode tabs (hwnd from ie_tabs) so the read and interact tools (ie_text, ie_html, ie_click, ie_fill, ie_js, ie_wait_text, ie_wait_element, ie_windows, ie_console, ie_screenshot scope=window ...) act on it without a target, over COM. The user keeps their login and page state. The tab's script instrumentation (see ie_console) is installed and stays in the tab until it is reloaded, even after ie_detach. ie_close needs ie_detach first (or force=true). Limits: no driver-only tools while attached (navigation, history, ie_wait_ready, page screenshot, upload: call ie_detach first), no proxy capture of the tab's traffic (only what the page's own instrumentation records), and a page's prompt cannot be answered (only alert and confirm windows pass the ie_dialog checks; answer a prompt yourself or ask the user). Keys, hover, window screenshots and ie_console work through COM and Win32.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "hwnd": "<hwnd>"
    },
    "name": "ie_attach"
  }
}

Input Schema

NameRequiredDescriptionDefault
hwndYeshwnd of the tab, from ie_tabs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.8/5.0
Behavior5/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 so thoroughly: it discloses that the user keeps login and page state, that instrumentation is installed and persists in the tab until reload even after ie_detach, that no proxy capture of tab traffic occurs, and that prompt dialogs cannot be answered (only alert/confirm pass ie_dialog). These are non-obvious side effects and constraints an agent could not infer from the schema.

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?

Purpose and target effect are front-loaded, and nearly every clause adds actionable information (limits, persistence, dialog constraint). The back half is a dense run-on of limitations that would scan better as a list, which keeps it from a 5.

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?

For a stateful, mode-establishing tool with no output schema, the definition covers what changes on attach, how long the state lasts, what becomes unavailable, and how to exit the mode. An agent has everything needed to call it and to predict its effect on subsequent calls.

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 single parameter has 100% schema coverage and the schema description already says 'hwnd of the tab, from ie_tabs', which the tool description restates. The guidance about using it as an implicit target for downstream tools adds context, but there is little parameter-specific meaning beyond the schema, so it sits slightly above the baseline.

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?

States a specific verb and resource ('Attach to one of the user's IE-mode tabs') plus the mechanism ('over COM') and the effect on siblings ('so the read and interact tools ... act on it without a target'). It also names where the hwnd comes from (ie_tabs), which cleanly separates it from the tab-listing and detach tools.

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

Usage Guidelines5/5

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

Explicitly covers when to use it (to give read/interact tools an implicit target) and when not to: driver-only tools — navigation, history, ie_wait_ready, page screenshot, upload — require ie_detach first, and ie_close needs ie_detach (or force=true). That is concrete exclusion guidance naming the exact sibling tools involved.

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