Skip to main content
Glama
Sign In
computer-use

computer-use

by Cassius-stack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

browser_list

Read-only

Lists available browsers and their open tabs, including live CDP, managed Chromium, and Safari/Chrome/Brave/Edge, with optional filtering by browser ID or name.

Instructions

List all available browsers (live CDP browsers, managed background 'iab' Chromium, Safari/Chrome/Brave/Edge) and their open tabs.

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

Input Schema

NameRequiredDescriptionDefault
browser_idNoOptional filter by browser ID or name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A3.6/5.0
Behavior3/5

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

readOnlyHint=true already establishes that this is a safe read. The description adds real value by disclosing the result composition (multiple browser backends, CDP vs managed 'iab' vs installed browsers, plus open tabs), but says nothing about result ordering, whether tab lists are truncated, or how many browsers may appear.

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 sentence that is front-loaded with the verb and resource and uses the parenthetical enumeration efficiently. There is no filler or redundant restatement of the name.

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-optional-parameter read-only tool with no output schema, the description adequately covers what comes back (browsers and their open tabs). It could have said more about result shape given there is no output schema, but the key expectation is set.

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 coverage is 100% and the single optional browser_id filter is fully documented in the schema as a filter by ID or name. The description never mentions filtering at all, so it adds nothing beyond the schema; baseline 3 applies.

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?

Names a specific verb (List) and resource (available browsers) and enumerates the categories returned: live CDP browsers, managed background 'iab' Chromium, and Safari/Chrome/Brave/Edge, plus their open tabs. That scope distinguishes it from list_apps and list_windows, though it never explicitly contrasts with those siblings.

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: an agent can infer this is the discovery call to run before browser_manage, browser_open_tab, or browser_tab_action. No explicit when-to-use or when-not-to-use guidance and no named alternative is given.

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