Skip to main content
Glama

Connect to a browser

connect_to_browser

Connect to CloudBrowser browser for direct control

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "browserAddress": "<browserAddress>",
      "sessionId": "<sessionId>"
    },
    "name": "connect_to_browser"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionIdYesUnique ID for the control session
browserAddressYesWebSocket URL of the CloudBrowser browser (format: ws://browser.cloudbrowser.ai/devtools/browser/[ID])

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare this is a non-read-only, non-destructive, non-open-world operation, so the safety profile is covered. The description adds nothing beyond that: it doesn't say what happens if a session already exists, whether the connection must later be closed with disconnect_browser, what errors occur on an invalid address, or what state the tool returns.

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?

A single front-loaded sentence with no filler or redundancy. It is efficiently worded, though its brevity reflects under-specification rather than deliberate economy.

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

Completeness2/5

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

For a connection-establishment tool with no output schema, the description should explain session lifecycle and result behavior, neither of which is present. An agent knows the verb but not the workflow contract around connecting, using, and disconnecting.

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%, with both browserAddress (including its ws URL format) and sessionId fully documented in the schema. The description adds no additional meaning about how these values are obtained or whether sessionId must be unique per connection, so the baseline of 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?

The description states a specific verb and resource ("Connect to CloudBrowser browser") plus the resulting capability ("direct control"), so an agent can tell this is a session-establishment call. It does not differentiate from siblings such as open_browser, resume_saved_session, or get_connected_browsers, leaving ambiguity about which connection path to pick.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus open_browser, resume_saved_session, or browser_workspace, and no statement of prerequisites such as already having a valid WebSocket address from open_browser or get_browsers. The agent must infer the whole workflow from sibling names.

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