Skip to main content
Glama
Sign In
Debug Web MCP

Debug Web MCP

by AYUSHchouhaan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

browser_stop_capture

Stop capturing events and return a summary of the temporary data collected during the session.

Instructions

Stop capture and return a summary of temporary event data.

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_stop_capture"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations the description carries the full burden. It does disclose that a summary of temporary event data is returned, but is silent on whether stopping clears/destroys that data, whether the session survives, or whether the events remain retrievable via browser_get_events.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no wasted words, well sized for a simple one-parameter tool.

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 stop tool with no output schema, the description is largely adequate, but it leaves the post-stop data lifecycle and session state ambiguous, which an agent needs in order to sequence calls against browser_get_events and browser_close_session.

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?

Schema description coverage is 0% and the description never mentions session_id, leaving the single required parameter undocumented. Though session_id is fairly self-evident, the description fails to compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Stop) and resource (capture) plus a hint at its output (summary of temporary event data). It is clearly the counterpart to the sibling browser_start_capture, though it never names that sibling explicitly.

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 only implied by the name pairing with browser_start_capture; there is no explicit statement of when to call it, what prerequisites (an active capture/session) are required, or how it relates to browser_close_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