Skip to main content
Glama

stop_browser

Stop and release a browser started with start_browser to prevent it from running until its TTL expires. Always call this when finished.

Instructions

Stop a browser started with start_browser and release it. Always call this when finished; an unused browser keeps running until its ttl expires.

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": {
      "browser_id": "<browser_id>"
    },
    "name": "stop_browser"
  }
}

Input Schema

NameRequiredDescriptionDefault
browser_idYesThe id returned by start_browser.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.2

TDQS

A4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden. It usefully discloses the resource-lifecycle behavior (the browser keeps running until ttl expires if not stopped, and stopping 'releases' it), but says nothing about idempotency, error behavior for an unknown/expired browser_id, or what is returned.

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 followed by the imperative and its rationale. Nothing is wasted and nothing important is buried.

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 and no annotations, this covers purpose, lifecycle pairing, and the consequence of skipping it. Only the failure/idempotency behavior for a stale browser_id is left unstated.

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?

There is a single parameter with 100% schema description coverage ('The id returned by start_browser'), so the schema does the heavy lifting. The description merely echoes that provenance ('started with start_browser') and adds no format or validity detail 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 ('Stop a browser') and anchors it to the sibling that creates it ('started with start_browser'), so an agent can tell it apart from list_browsers or cancel_job without opening any schema.

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?

Explicit invocation guidance: 'Always call this when finished', plus the reason (unused browser runs until ttl expires). It gives a clear when but does not cover edge cases such as calling it after the ttl already expired or on an already-stopped browser.

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