Skip to main content
Glama
Sign In
agent-browser-mcp

agent-browser-mcp

by zy2755
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

browser_close

Closes the browser or disconnects the session: launch mode exits Chrome/Edge and keeps profile login state, while connect mode drops only the connection; the next tool call restarts automatically.

Instructions

关闭浏览器(launch 模式下整个浏览器退出,profile 登录态保留;connect 模式只断开连接)。下次工具调用会自动重启。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the burden and does add real behavioral detail: in launch mode the whole browser process exits, in connect mode only the connection drops, profile login state survives, and the next call restarts. It omits what happens if no browser is running and whether any unsaved page state is discarded.

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 compact clauses, action first, then mode-dependent outcome and recovery behavior. Every clause carries information; nothing is padding.

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 zero-parameter, no-output-schema tool this is close to complete: it explains mode-dependent effects and the auto-restart recovery path. A short note on the state when no browser is active would make it fully sufficient.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The mode distinction it describes is a property of the server configuration, not a parameter the agent supplies.

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+resource ('关闭浏览器') and immediately distinguishes two operating modes (launch vs connect) with what each does. No sibling tool covers closing, and the agent can tell exactly what this does without opening a schema.

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 context is implied through the note that the next tool call auto-restarts the browser, which reassures the agent it is safe to call mid-session. However, there is no explicit 'use this when' / 'do not use when' guidance, nor any stated prerequisite such as a browser having to be open first.

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