Skip to main content
Glama

ie_close

Close the IE-mode session and quit Edge. Use force=true to cancel running waits and kill a stuck browser or dialog without contacting the driver.

Instructions

Close the IE-mode session and quit the browser. The session name stays reserved for this server; ie_open starts a new browser. With force=true, running waits are cancelled and this session's own IEDriver and Edge are killed (only if they are still the recorded processes) without calling the driver at all: use it when a call hangs or the page is stuck in a dialog.

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

Input Schema

NameRequiredDescriptionDefault
forceNocancel waits and kill the browser without asking the driver (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses that force=true cancels running waits, kills this session's own IEDriver and Edge, deliberately bypasses the driver, and is guarded to only kill processes still recorded for the session. It doesn't cover failure modes, such as what happens when no session is open.

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?

Three sentences, front-loaded with the core action, then the session-lifecycle consequence, then the escalation path. No filler; every clause carries operational meaning.

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?

For a single-optional-param teardown tool with no output schema and no annotations, the description covers side effects, safety conditions, and escalation triggers well. The remaining gap is error/lifecycle edge cases, such as behavior with no active session.

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% and the sole force parameter is already documented, so the schema does the heavy lifting. The description adds marginal value by naming the use case for force and the safety guard around process killing, but nothing about types or defaults beyond the schema.

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 ('Close the IE-mode session and quit the browser') and immediately distinguishes its scope from ie_open, which starts a new browser. An agent can tell what this tool does and how the session lifecycle continues after it.

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 says when force=true applies ('use it when a call hangs or the page is stuck in a dialog') and implies the default path by noting the default is false and that the session name stays reserved. It even tells the agent that ie_open is the follow-up action.

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