Skip to main content
Glama
RobithYusuf

mcp-stealth-chrome

by RobithYusuf
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

tab_focus

Bring the current browser window to the foreground after automated navigation, so you can see what MCP is doing. Resolves hidden windows due to profile fallback or minimized state.

Instructions

⭐ Bring the active tab's browser window to the OS foreground.

Programmatic CDP navigation does not raise Chrome to the front, so
on a desktop where the user has their own Chrome already open you
may see only the original window even though MCP successfully
drove a different window/tab. Call this when you want to *see*
what MCP is doing.

Common reasons MCP's window is hidden:
  - Per-PID profile fallback: another Chrome already held
    ~/.mcp-stealth/profile/, so MCP launched into
    ~/.mcp-stealth/profile-pid<N>/ — that's a SEPARATE Chrome window.
    Run server_status to confirm (profile_dir field).
  - OAuth popup opened a new tab/window MCP now drives.
  - macOS Spaces / minimized window / behind other apps.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.5/5.0
Behavior4/5

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

With no annotations provided, the description carries full burden. It discloses that the tool brings the window to the foreground and explains why it's needed, including specific reasons for hidden windows. It does not mention side effects or failure cases, but the behavior is straightforward.

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?

The description is concise, well-structured with a star emoji, and uses bullet points for common reasons. Every sentence adds value, and the main action is front-loaded.

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 no parameters and an output schema, the description fully explains the tool's purpose, usage scenarios, and rationale. It is complete for a simple focus operation.

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 no parameters, so the baseline is 4 as per instructions. The description does not add parameter-specific information, but none is needed. The context about when to use the tool adds value beyond 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 description clearly states the tool brings the active tab's browser window to the OS foreground, with a specific verb+resource. It explains the need due to programmatic CDP limitations, distinguishing from other sibling tools like tab switching or navigation.

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 explicitly states when to call ('when you want to *see* what MCP is doing') and lists common scenarios where the window might be hidden. However, it does not explicitly mention when not to use or suggest alternatives, though the context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/RobithYusuf/mcp-stealth-chrome'

If you have feedback or need assistance with the MCP directory API, please join our Discord server