agent-browser-mcp

Overview Schema Source Related Servers Discussions Admin

get_setup_status

Idempotent

Diagnose browser extension setup by returning component versions, build verdicts, and connection status to identify stale processes or missing tokens.

Instructions

Return component versions, stale-build actions, extension path, bridge ports, and connection status for setup/diagnostics. extension_build_verdict answers whether the browser worker is running this code (matches_tree / stale_worker), or says why it cannot tell (stamp_not_regenerated / unverifiable); it is decisive where version equality is not. extension_build_enforced=false means no comparison happened, so treat it as unknown rather than as a pass. extension_status_available=false means no runtime status was obtained: starting asks to wait_for_extension, then extension_unavailable asks to check_extension_connection; missing status alone never requests a reload. mcp_build_verdict and bridge_build_verdict compare each process's package-import Python and imported JavaScript source snapshot with expected_python_source_identity on disk: matches_tree, stale_process, or unverifiable. Same-version source changes require restart_mcp_session or restart_bridge; *_build_enforced=false is unknown. state_paths distinguishes missing/empty/ready/unreadable/invalid_encoding token files without exposing token content; unreadable metadata has unknown existence. On Windows, inspecting an existing token file may tighten its ACL to the current user. Bridge startup or authentication initialization may create a missing token file. A malformed remote diagnosis reports bridge_unreachable with malformed_diagnosis, not evidence of an old build. Answers while another tool is still running; default_session_id is isolated from other calls' temporary targets. capability_registry reports declared/registered tool counts, completeness and page/browser/desktop groups. Each tool's MCP annotations describe its potential effects.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 5, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Discloses significant non-obvious behavior beyond annotations: possible Windows ACL tightening, token file creation during bridge startup/auth initialization, answering while another tool is still running, session isolation, and malformed remote diagnosis handling. These complement and align with the annotations rather than contradicting them.

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?

The description is front-loaded with the core purpose and each sentence adds diagnostic nuance, but it is extremely dense and runs as one long paragraph. It could be tightened with bullet-style grouping, though it stays on-topic and avoids filler.

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?

Given the output schema already exists and there are no input parameters, the description is remarkably complete: it covers every verdict family, special false/unknown values, side effects, concurrency behavior, and even Windows-specific behavior. An agent has enough context to invoke and interpret this tool correctly.

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 has zero parameters and the input schema is empty, so there are no parameter semantics to document. Schema description coverage is 100% and the no-parameter baseline of 4 applies; the description correctly spends no effort on parameters.

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 description opens with a specific verb and resource: 'Return component versions, stale-build actions, extension path, bridge ports, and connection status for setup/diagnostics.' It enumerates concrete output categories and clearly frames the tool as a setup/diagnostics status tool, distinguishing it from sibling tools like extension_path or get_automation_profile.

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?

The description gives clear context for when to rely on its results and maps diagnostic verdicts to follow-up actions: 'wait_for_extension', 'check_extension_connection', 'restart_mcp_session', and 'restart_bridge'. It does not explicitly name sibling alternatives or when-not conditions, but the action mappings effectively convey usage guidance.

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

Deploy Server