Skip to main content
Glama

stop_browser

Close a specific instance's browser and its tabs without affecting other instances; attached browsers are disconnected only.

Instructions

Stops an instance's browser and closes its tabs; other instances keep running. A browser the server attached to (not launched) is only disconnected.

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": "stop_browser"
  }
}

Input Schema

NameRequiredDescriptionDefault
instance_idNoDefault: '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, the description carries the full burden and does meaningful work: it discloses that tabs are closed, that other instances are unaffected, and that server-attached browsers are merely disconnected rather than terminated. It omits idempotency, error behavior when no browser is running, and any return signal, which keeps it short of a 5.

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 sentences, no filler, with the primary effect stated first and the important attached-versus-launched caveat second. Every clause contributes information an agent would otherwise have to guess.

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 one-parameter teardown tool with no output schema, this is nearly complete: effect, blast radius, and the attach-mode exception are all covered. Only edge-case behavior (no running browser, repeat calls) is unaddressed.

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?

The single instance_id parameter is already fully documented in the schema, including the 'default' fallback. The description reinforces per-instance scoping ("an instance's browser", "other instances keep running") but adds no new semantics about the parameter itself, which matches the baseline for 100% schema coverage.

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 and resource ("Stops an instance's browser") plus its immediate effects ("closes its tabs"). The scope clause "other instances keep running" separates it from panic-button shutdowns, though it never names close_instance or restart_browser to make the boundary explicit.

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 by the described effect and the scoping note about other instances, but there is no explicit when-to-use or when-not-to-use instruction, and no named alternative such as close_instance or restart_browser. An agent must infer the choice from sibling names alone.

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