Skip to main content
Glama

Browser sessions

browser_workspace
Read-only

Show your active browsers and saved sessions in a workspace beside the conversation. Does not allocate or connect a browser. Optionally show a connected browser and its current screenshot. Use the sessionId and address from the selected browser to continue work.

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

Input Schema

NameRequiredDescriptionDefault
browserAddressNoOptional owned browser to inspect.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: it clarifies the tool only displays a workspace pane and explicitly does not allocate or connect a browser, which prevents an agent from expecting lifecycle side effects.

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?

Front-loaded with the primary action and kept to four short sentences with no filler. The closing sentence about the 'sessionId and address' is slightly ambiguous since sessionId is not a parameter and no output schema documents it, but the overall shape is efficient.

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 zero-required-parameter display tool, the description covers what appears, what does not happen, and what the agent gets back to continue work. The only gap is the origin of sessionId, which is not described anywhere since there is no output schema.

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?

With a single parameter at 100% schema coverage the schema already defines browserAddress as an optional owned browser to inspect. The description reinforces this by saying it optionally shows a connected browser and its current screenshot, but adds no format, validation, or selection detail beyond that.

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 and resource: 'Show your active browsers and saved sessions in a workspace beside the conversation.' The negative clause 'Does not allocate or connect a browser' separates it from open_browser/connect_to_browser, though it never distinguishes the workspace pane from the data listings returned by get_browsers/get_saved_sessions.

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: the agent learns it can optionally surface a connected browser with its screenshot, and that sessionId/address feed follow-on work. There is no explicit statement of when to call this versus listing sessions with get_saved_sessions or inspecting browsers with get_browsers, and no prerequisites are given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources