Skip to main content
Glama

close_instance

Stops a browser-control instance by its ID; non-default instances are removed, while the default instance stops and relaunches automatically on next use.

Instructions

Stops an instance: other instances are removed; 'default' is stopped and relaunched on its next use.

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": {
      "instance_id": "<instance_id>"
    },
    "name": "close_instance"
  }
}

Input Schema

NameRequiredDescriptionDefault
instance_idYesDefault: 'default'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-rc.1

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations provided, the description carries the full behavioral burden and does disclose important side effects: other instances are removed, and the 'default' instance is stopped but relaunched on next use. This is meaningful context beyond the bare action, though the phrase 'other instances are removed' is somewhat ambiguous and no error or reversibility details are given.

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?

The description is a single front-loaded sentence with no wasted wording. The colon and semicolon structure make it efficient, though the 'other instances are removed' clause is slightly unclear.

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 simple one-parameter stop tool with no output schema, the description covers the core action, side effects, and special default-instance lifecycle. It could be more complete by clarifying the scope of 'other instances are removed', but the essential context is present.

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?

Schema coverage is 100%, so the baseline is 3. The description adds useful meaning about the 'default' value of instance_id: it is stopped and relaunched on next use, which is special behavior not captured by the schema's brief default note.

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?

The description opens with a specific verb and resource: 'Stops an instance'. This clearly distinguishes it from tab and browser operations by naming the instance resource. It does not explicitly compare itself with siblings such as close_tab or stop_browser, so it falls short of the strongest sibling differentiation.

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 only implied through the action 'Stops an instance' and the note about the 'default' instance. There is no explicit when-to-use guidance, no when-not-to-use conditions, and no stated alternative tools for different close/stop scenarios.

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