Skip to main content
Glama
Sign In
Browser Bridge MCP

Browser Bridge MCP

by adbarc92
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

browser_send_message

Send custom messages to the Chrome extension to extend browser automation capabilities beyond standard actions.

Instructions

Send a custom message to the Chrome extension for extensibility

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": {
      "type": "<type>"
    },
    "name": "browser_send_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataNoOptional data payload
typeYesCustom message type

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided, so description must fully disclose behavioral traits. It only states 'custom message' without mentioning side effects, state changes, destructive potential, or permission requirements. The phrase 'for extensibility' is too vague to inform an agent about consequences.

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?

Single sentence, front-loaded with action and resource. No redundancy. Although brief, it earns its place by being direct. Could be slightly expanded for better guidance.

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

Completeness3/5

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

Given the high schema coverage and lack of output schema, the description is minimally adequate. However, it lacks context on typical use, error behavior, or interaction with other browser tools. An agent may not know when or how to invoke it effectively.

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 description coverage is 100% with both parameters documented. The description adds 'custom message type' and 'optional data payload', but these merely echo schema descriptions. No additional meaning or constraints are provided beyond the schema.

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?

Description clearly states verb 'Send' and resource 'custom message to the Chrome extension', with purpose 'for extensibility'. It distinguishes from siblings like browser_navigate or browser_click by being a generic message-sending tool. However, it doesn't specify what types of messages are possible or their effects.

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?

No guidance on when to use this tool versus alternatives like browser_evaluate or browser_get_content. The description lacks context about use cases, prerequisites, or conditions under which sending a custom message is appropriate.

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