SoftGlaze Browser MCP

Overview Schema Source Related Servers Discussions Admin

Stop all profiles

stop_all_profiles

Idempotent

Close all visible browser profiles in your token groups, or only those started by AI apps; requires user approval each time.

Instructions

Closes every running profile you can see (within this token's groups), or only those AI apps started (onlyStartedByAi). Asks the user every time.

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": "stop_all_profiles"
  }
}

Input Schema

Name	Required	Description	Default
`onlyStartedByAi`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 10, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare non-read-only, idempotent and non-destructive; the description earns credit for disclosing the confirmation prompt ('Asks the user every time') and the token-scoped visibility limit, which are not expressed in structured fields. It does not say what happens to profiles mid-run or whether partial failures are reported.

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 front-loaded sentence with the scope constraint and the optional filter, plus a short behavioral note. No filler or repetition of the title.

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 one-parameter bulk mutation with no output schema and reasonably informative annotations, the description covers scope, the filter, and the confirmation requirement. Return/reporting behavior after a batch stop is the main omission.

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?

Schema coverage is 0%, so the description must carry the load, and it does explain the sole parameter's meaning ('only those AI apps started'), which the bare boolean property does not. The default behavior when the flag is omitted is implied ('every running profile') but not stated explicitly.

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 states a specific verb and resource ('Closes every running profile') plus a scope qualifier ('within this token's groups'), which is enough for an agent to distinguish the bulk operation from the singular stop_profile sibling, even though that sibling is not named.

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?

It implies bulk use ('every running profile') and gives one branch condition (onlyStartedByAi), but never states when to prefer this over stop_profile for a single target, nor any exclusion such as profiles outside the token's groups being silently ignored.

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