Skip to main content
Glama
Sign In
DrissionPage-MCP

DrissionPage-MCP

by hooplus1ce
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

关闭浏览器

browser_close
Destructive

Terminate an active browser session and release its resources. Use force to kill the underlying process if needed.

Instructions

关闭并移除一个浏览器会话（browser_connect 接管的浏览器只断开连接不退出）。

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

Input Schema

NameRequiredDescriptionDefault
forceNo是否强制结束浏览器进程
browser_idYes浏览器会话 id，可用 browser_status 查询

Output Schema

NameRequiredDescriptionDefault
okYes
messageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

The description indicates a destructive action (close and remove), and the destructiveHint annotation further confirms this. It also clarifies that unlike browser_connect, this tool actually exits the browser. However, it does not detail potential side effects like terminating all associated processes or closing all tabs, though the contrast helps. Since the annotation already signals destructiveness, the description adds sufficient context.

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?

The description is concise, consisting of a single sentence that clearly conveys the tool's purpose and the key contrast with browser_connect. It contains no unnecessary words or redundancy.

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

Completeness5/5

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

For a simple browser-closing tool, the description is complete. It defines the action, contrasts with a related tool, and is sufficient for an agent to understand when and how to use it. No additional details about return values or errors are necessary for this basic operation.

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 schema provides descriptions for both parameters (browser_id and force), covering 100% of the parameters. The tool description itself does not add additional meaning beyond the schema, so it meets the baseline but does not exceed it.

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?

The description clearly states the tool closes and removes a browser session, using the specific verb '关闭并移除' (close and remove). It also distinguishes itself from browser_connect by noting that browser_connect only disconnects without exiting, making the purpose unambiguous.

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

Usage Guidelines5/5

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

The description provides explicit usage guidance by contrasting with browser_connect: when you need to actually close and exit a browser session, use browser_close; when you only need to disconnect, browser_connect is appropriate. This clarifies when to choose this tool over alternatives.

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

Deploy Server

Other Tools