Skip to main content
Glama
Sign In
Debug Web MCP

Debug Web MCP

by AYUSHchouhaan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

browser_close_session

Close a Debug Web debugging session by detaching from the browser, closing only the debug socket, and discarding temporary data while leaving Chrome and its tab open.

Instructions

Detach, close only Debug Web's socket, and discard temporary data; leaves Chrome and the tab open.

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": {
      "session_id": "<session_id>"
    },
    "name": "browser_close_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose the key behavioral traits: what is destroyed (temporary data discarded) and what survives (Chrome and the tab remain open). It omits error behavior and whether the session_id can be reused, so a 4 rather than a 5.

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 sentence with no waste, and the destructive scope is front-loaded ahead of the survival guarantee.

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

Completeness3/5

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

For a simple one-param teardown tool with no output schema this is nearly sufficient behaviorally, but the lone parameter is left unexplained in both schema and description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one required parameter (session_id) with 0% schema description coverage, and the description never mentions it, so the agent gets no meaning for the argument beyond its name. With a parameter present and undocumented, the baseline can't be the 0-parameter 4.

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 ('detach, close') and resource ('Debug Web's socket'), and explicitly scopes what is NOT touched ('leaves Chrome and the tab open'), which distinguishes it from browser_open_session and from any imputed browser-shutdown behavior.

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?

No explicit when-to-use or alternative names, but the clause 'leaves Chrome and the tab open' implies the scenario (detaching while preserving the browser), which is enough for implied usage but not for a 4.

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