Skip to main content
Glama

ie_open

Starts or reuses a Microsoft Edge IE-mode session and opens an http(s) URL, keeping it alive for later calls.

Instructions

Start (or reuse) an Edge IE-mode session and navigate to a URL (default IE_DEFAULT_URL). Keeps the session alive for later calls. An http(s) URL is required in IE mode: about:blank renders in Chromium and IEDriver cannot find an IE window, so a new session opened on it fails.

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

Input Schema

NameRequiredDescriptionDefault
urlNoURL to open (default about:blank)
waitNoseconds to wait after load (default 4)

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?

No annotations are supplied, so the description carries the full burden, and it does real work: it discloses session persistence ('keeps the session alive for later calls') and a specific failure mode (about:blank renders in Chromium, IEDriver cannot find an IE window, the new session fails). It does not cover what happens on a failed navigation or whether a partial session is left behind.

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?

Three sentences, front-loaded with the action and then the behavioral caveats, with no filler. The final sentence is dense and slightly convoluted but every clause carries information an agent needs to avoid a failed call.

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?

Covers purpose, persistence semantics, the critical URL constraint, and the load-wait default — enough to invoke it correctly. With no output schema, it never says what is returned (a session handle, a page object), which is the main remaining gap.

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

Parameters3/5

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

Schema coverage is 100%, so the schema already explains both parameters, and the description adds the useful rationale for the http(s) constraint. However, it conflicts with the schema: the description says the default is IE_DEFAULT_URL while the schema says default about:blank, and the description calls url effectively required while the schema marks zero required parameters.

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 concrete verb and resource — start or reuse an Edge IE-mode session and navigate — which is distinguishable from the sibling ie_goto (navigate an existing session) and ie_attach (attach to a running one). It stops short of naming those alternatives, so the differentiation is inferred rather than stated.

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?

Clear usage context: this is the entry point that opens a session and keeps it alive for later calls, and the http(s) requirement tells the agent when a call will fail. It does not explicitly say 'use ie_attach instead if a session already exists outside this tool', which is the one remaining inference.

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