Skip to main content
Glama
Sign In
Fast Browser MCP

Fast Browser MCP

by kqlio67
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

browser_stop_coverage

Stop active V8 code coverage measurement and retrieve executed scripts and functions, with optional URL filtering and a setting to return only functions that ran.

Instructions

Stop active V8 code coverage measurement and return executed scripts and functions.

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

Input Schema

NameRequiredDescriptionDefault
url_filterNoOptional substring filter for script URLs
only_executedNoOnly return functions with call count > 0

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.12.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It says the tool stops measurement and returns data, but does not disclose whether existing coverage data is discarded, whether measurement must already be active, what permissions are needed, or how the stop affects subsequent coverage queries.

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?

The description is a single front-loaded sentence with no wasted words. It states the action and immediate result efficiently.

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 simple two-parameter tool with full schema coverage, the description covers the core action and return payload. The absence of an output schema is partially compensated by 'return executed scripts and functions', though it could clarify the relationship to the coverage lifecycle.

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

Parameters3/5

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

Schema description coverage is 100%, so url_filter and only_executed are already well documented in the input schema. The description adds no parameter-specific meaning beyond what the schema provides, making the baseline score of 3 appropriate.

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?

The description uses a specific verb ('Stop') and resource ('active V8 code coverage measurement') and states the return payload. It is clearly a stop operation, but it does not explicitly distinguish itself from sibling tools such as browser_start_coverage or browser_observe_coverage.

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 by 'Stop active ... measurement', suggesting it should be called after coverage has been started. However, the description does not explicitly state when to use this tool instead of observe_coverage or start_coverage, nor does it mention prerequisites like an active measurement 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