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

pony-browser-mcp

by pssrh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

browser_use_workspace

Switch the active Chrome tab group to a named task group, creating it if missing. Organize browsing by task for cleaner workspaces.

Instructions

Switch the active Chrome tab group to a task name. Creates the group if missing.

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

Input Schema

NameRequiredDescriptionDefault
nameNoAlias for task
taskNoTask / tab group name (preferred)
groupNoAlias for task
workspaceNoAlias for task

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.8/5.0
Behavior3/5

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

Without annotations, the description carries the behavioral burden. It does disclose a key side effect, 'Creates the group if missing,' but it does not explain what happens to existing tabs, whether the operation is reversible, or what the result or failure behavior looks like.

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 two short sentences, front-loaded with the primary action and immediately followed by the important create-if-missing behavior. There is no filler or redundant phrasing.

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 low-complexity tool with no output schema and aliased parameters, the description is largely complete: it explains the main action, the condition for creation, and the core input concept. The main gap is the lack of explicit when-to-use or alternative guidance, which is already reflected in the usage_guidelines score.

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 the schema already documents all parameters and their alias relationships. The description reinforces that a 'task name' is the input, but it does not add meaningful detail beyond the schema.

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 specific action and resource: 'Switch the active Chrome tab group to a task name.' It also clarifies the create-if-missing behavior, which distinguishes it from sibling tools like browser_switch_tab or browser_cleanup_workspace.

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?

The usage is implied: call this tool when you want the active Chrome tab group to correspond to a task name. However, it does not explicitly state when not to use it or mention alternatives such as browser_list_tabs or browser_switch_tab.

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