Skip to main content
Glama

ie_detach

Detaches from the attached tab, returning tool control to the IE driver session while leaving page instrumentation active until reload.

Instructions

Detach from the attached tab: the tools go back to the IE driver session. The page's instrumentation stays in the tab until it is reloaded.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does well on the core side effect — tool routing reverts to the driver session — and flags the notable caveat that instrumentation persists in the tab until reload. It omits what happens to the tab itself, whether other attached tabs are affected, and whether re-attaching restores state.

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?

Two short sentences, front-loaded with the action and its immediate consequence, followed by the one non-obvious caveat. No filler.

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 parameterless state-toggle tool with no output schema and no annotations, the description covers what changes and the lingering-instrumentation gotcha. A sentence on interaction with ie_attach/ie_tabs would make it fully complete.

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 zero parameters, so the baseline is 4; there is nothing for the schema to document and nothing the description needs to compensate for.

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 specific verb ('Detach') and resource ('the attached tab') plus the resulting state ('tools go back to the IE driver session'). It is clearly the inverse of the ie_attach sibling, though it never names that sibling explicitly.

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 rather than stated: an agent can infer you call this when you no longer want tools targeting the attached tab. There is no explicit 'use this when...' clause, no mention of ie_attach as the counterpart, and no guidance on whether detaching is required before attaching elsewhere.

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