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

browser-keyboard-mcp

by s-hiraoku
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

browser_close

Destructive

Ends the current session by releasing active keys and closing the dedicated browser to stop input.

Instructions

Stop input, release keys, and close the dedicated browser.

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.2/5.0
Behavior4/5

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

Annotations already mark it destructive, but the description adds valuable order of operations: first stop input, then release keys, then close the browser. It also names the uniquely dedicated browser, providing context beyond the bare annotation.

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?

A single concise sentence covers the purpose and action sequence with no wasted words. Every element—stop, release, close—adds meaning.

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?

The description is sufficient for a parameterless destructive close operation. It tells the agent exactly what will happen and the order of operations. It could mention the connection to browser_open but the 'dedicated browser' wording implies a managed session, so it is acceptable.

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 has zero parameters, so the schema needs no explanation. The description is accurate; baseline 4 applies because there are no parameters to describe.

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 states a clear, specific sequence of actions: stop input, release keys, and close the dedicated browser. This distinguishes it from siblings like release_all and browser_open without requiring schema inspection.

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 is implied but not explicit. The description conveys that this is the cleanup action that both releases keys and closes the browser, which hints at when to use it, but it does not explicitly name alternatives or state conditions such as 'use when done with the browser session'.

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