Skip to main content
Glama

Close a browser

close_browser
Destructive

Close a specific browser

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": {
      "address": "<address>"
    },
    "name": "close_browser"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesAddress of the browser to close

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that: it does not say whether the session, tabs, or unsaved state are lost, whether the browser process is terminated or merely detached, or whether the action is reversible. For a destructive operation, that is a meaningful gap.

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?

Four words, front-loaded, with zero filler or redundancy. It is efficient, though the brevity comes at the cost of the substance missing elsewhere rather than through elegant compression.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (one required parameter, no output schema) and annotations cover the destructive profile, so the bar is modest. Still, for a destructive close operation sitting beside disconnect_browser and open_browser, the description leaves the critical distinction and the consequences of the action unexplained.

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, so the schema fully documents 'address'. The description's phrase "a specific browser" is consistent with that but contributes no format, source, or lookup guidance beyond the schema, making baseline 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Close a specific browser" is essentially the tool name and title restated as a sentence. The only added nuance is the word "specific," which faintly signals that a single target is addressed by identifier. It gives an agent no basis for distinguishing this from siblings such as disconnect_browser, open_browser, or remove_saved_session.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to close versus disconnect, when a browser should be left running, or what preconditions apply (e.g., must it be connected first?). The agent must infer the usage context entirely from the tool name.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources