Skip to main content
Glama
mcp-cui-chrome

mcp-cui-chrome

by cuipy

关闭浏览器

browser_close

Closes the Chrome window opened by the current session; if another session owns the window, it disconnects without closing it.

Instructions

通用:关掉这次会话自己打开的 Chrome。如果窗口是别的会话打开的,只断开连接,窗口留着。

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.0.4

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations present, the description carries the full disclosure burden, and it delivers the single most non-obvious trait: ownership-sensitive behavior that closes your own browser but merely detaches from another session's window. It omits idempotency (what happens if nothing is open), whether unsaved page state is discarded, and whether an error or a success signal 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, zero filler, with the scope qualifier ('this session's own Chrome') front-loaded before the conditional branch. Every clause carries distinct information.

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 teardown tool with no annotations and no output schema, the description covers the essential surprise — that it may not actually close the window. Only edge-case behavior (no browser open, confirmation of success, effect on other open tabs) remains unstated.

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 the baseline is 4; there are no argument semantics for the description to clarify. Nothing in the text misleads about inputs.

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 names a specific verb and resource ('关掉这次会话自己打开的 Chrome' — close the Chrome this session opened) and immediately bounds the scope to the caller's own session. That scope statement makes it unmistakable against siblings like browser_navigate or browser_tabs, which manage content rather than lifecycle.

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?

It makes clear the tool applies to the browser this session launched, and it states the alternative handling when the window belongs to another session (disconnect only). It does not spell out the triggering situation ('use when finished with browsing') or whether calling it with no open browser is safe, so it falls short of a full when/when-not statement.

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