Skip to main content
Glama
Browser MCP Server

Browser MCP Server

by xiaoguangpan

connect

Verifies whether the browser extension is linked to the MCP server so AI clients can confirm browser control is available before running operations.

Instructions

Check if browser extension is connected

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. 'Check' implies a non-mutating probe, but nothing is said about what a failed check looks like, whether it errors or returns a false status, or whether it has any side effects such as triggering a connection attempt — a meaningful ambiguity for a tool literally named 'connect'.

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 with zero filler and the key fact (connected vs. not) front-loaded. Nothing is wasted or buried.

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?

With no annotations and no output schema, the description is the only source of truth about return behavior, and it never says what a 'connected' result looks like or what happens when the extension is absent. For a tool whose entire value is a status outcome, that gap matters more than for a simple parameterless call.

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, so there is nothing for the description to disambiguate. Baseline 4 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 names a specific verb ('Check') and object ('browser extension is connected'), which usefully disambiguates the vague tool name 'connect' — it is a status probe, not the act of connecting. It does not, however, reference any sibling such as open_tab or tabs to anchor where this check sits in a workflow.

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 statement of when to call this versus the other browser tools; the natural guidance (call before navigate/open_tab/click to verify the extension is available, and how to react if it is not) is left entirely implicit. The agent must infer its place in the sequence.

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