Skip to main content
Glama
Sign In

BrowserPair

by com.browserpair.mcp
OverviewDiscussionsAdmin

List paired browsers

browser_list
Read-onlyIdempotent

List the user's Chrome profiles this BrowserPair connection may use and whether each is online. Each label is the name the user gave that profile (for example "Work profile"): when the user names a browser, use the one whose label matches; when several are online and the user named none, ask which one. Read-only.

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the trailing "Read-only." is largely redundant. The genuinely additive content is the shape of the result: one entry per profile with a user-supplied label and an online indicator, which is behavioral detail the annotations cannot convey.

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?

Three sentences, front-loaded with what is returned, then the disambiguation rule, then a safety note. The closing "Read-only." duplicates the annotations and could be cut without loss; everything else earns its place, including the concrete "Work profile" example that makes the label-matching rule concrete.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no parameters and no output schema, the description carries the burden of describing the return value and does so concretely (labels plus online status). Combined with annotations covering the safety profile and the label-matching rule covering agent behavior, nothing needed to call this correctly 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 no parameters, so the baseline of 4 applies; there is nothing for the description to disambiguate. It correctly spends no words on inputs and instead invests them in interpreting the output labels.

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?

States a specific verb and resource ("List the user's Chrome profiles this BrowserPair connection may use") plus the per-item payload (online status), which cleanly separates it from browser_run, the only sibling that acts on a browser. An agent can tell what it gets back without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly covers the selection case: match the profile whose label equals the user's naming, and when several are online and the user named none, ask rather than guess. What's missing is an explicit pointer that browser_run is the follow-up action once a profile is chosen, so the routing to the sibling is implied rather than stated.

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

All BrowserPair toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources