Skip to main content
Glama

list_browsers

Retrieves every browser in the workspace, including burners and saved identities, with its status so you can choose the correct browser for a task.

Instructions

List this workspace's browsers (burners and saved identities) with their status.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.2

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden; "List" implies a read-only, non-destructive operation and it discloses that status is included in the result. It says nothing about result ordering, volume, pagination, or whether stopped/expired browsers appear, which is the behavioral detail an agent would want before calling.

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?

One short sentence, front-loaded with the verb and resource, with the clarifying parenthetical placed where it is most useful. There is no filler or repetition.

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-parameter list tool with no output schema, the description covers what is returned (browsers of two kinds) and that status is included. Minor gaps remain about return shape and whether all browser states are listed, but nothing essential for correct invocation is missing.

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?

The tool takes zero parameters and the description introduces none, so there is no parameter meaning to explain. The baseline of 4 applies; the implicit scoping to the current workspace is a small bonus that clarifies why no workspace argument is needed.

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 gives a specific verb and resource ("List this workspace's browsers") and even disambiguates the term by naming the two kinds returned ("burners and saved identities") plus their status. It stops short of distinguishing itself from the sibling list_identities, which plausibly returns overlapping data, so a 4 rather than a 5.

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 phrase "this workspace's" signals scope, and the mention of status hints at a monitoring/inspection use case. There is no explicit when-to-use versus list_identities, nor any statement of when this tool is not appropriate.

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