Skip to main content
Glama
frsorrentino

Chrome Bridge

by frsorrentino
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_status

Idempotent

Report Chrome Bridge status and capabilities when a tool is missing or browser commands fail; enable caps for this session.

Instructions

Status of the bridge itself, not of a page: call it when a tool you expect is missing or browser commands fail (connected=false: the extension is not reachable). Also reports mode (primary/relay), host, port, server and extension versions, js_evaluation (false under --no-js), write_root, read_root, session_tab_id (the implicit tab), owned_tabs (created by this session), uptime_sec. caps_active and caps_available: a missing tool lives in an inactive cap. enable is the only change it makes: it switches caps on for this session, no restart, and lists the tools added. Optional caps: audits (cookie_audit); visual (inject_css, measure_spacing, emulate_media, viewport_resize); perf (animations, frames, perf_trace, screencast, lighthouse, heap_snapshot); network (http_auth, set_geolocation, track_events); storage (get_storage, set_storage, session_fixture); dom (modify_dom, watch_dom, drag_and_drop); files (save_page, manage_downloads, session_record).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
enableNoCaps to switch on now, all in one call; "all" = every cap

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.28.0
    • addedInput schema / properties / enable
      Added value: +{
+  "description": "Caps to switch on now, all in one call; \"all\" = every cap",
+  "items": {
+    "enum": [
+      "all",
+      "audits",
+      "visual",
+      "perf",
+      "network",
+      "storage",
+      "dom",
+      "files"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}
  2. First observedv1.8.0

TDQS

A4.5/5.0
Behavior5/5

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

With readOnlyHint=false, the description carries the burden of explaining the mutation, and it does: 'enable is the only change it makes: it switches caps on for this session, no restart, and lists the tools added.' This confirms idempotency semantics and scopes the write precisely, adding context the annotations alone do not provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, which is good, but the body is a dense run-on paragraph with heavy parenthetical nesting, and the trailing list of every cap-to-tool mapping is bulky. Most content earns its place given the missing output schema, but the structure is poor.

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?

There is no output schema, so the description correctly enumerates the returned fields (mode, host, port, versions, js_evaluation, write_root, read_root, session_tab_id, owned_tabs, uptime_sec, caps_active, caps_available) and explains the enable side effect. An agent has everything needed to call and interpret this diagnostic tool.

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?

Schema coverage is 100%, so the baseline is 3, but the description goes further by mapping each cap value (audits, visual, perf, network, storage, dom, files) to the concrete tools it unlocks. That is meaningful added context for choosing enable values beyond the enum listing in the schema.

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?

The opening clause states a specific resource and scope: 'Status of the bridge itself, not of a page.' This immediately distinguishes it from page-oriented siblings like get_page_info, and the enumeration of reported fields (mode, host, port, versions, session_tab_id, caps) makes the resource concrete.

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?

It gives an explicit trigger ('call it when a tool you expect is missing or browser commands fail') and a diagnostic reading (connected=false means the extension is unreachable), plus the enable use case. It does not name a sibling alternative to reach for instead in other situations, so it falls short of a full 5.

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