Skip to main content
Glama
Codex Control Chrome MCP

Codex Control Chrome MCP

by iola1999

chrome_status

Displays native host manifest paths and discovered bridge socket locations, helping verify Chrome extension bridge configuration and troubleshoot connection issues.

Instructions

Show native host manifest paths and discovered bridge sockets.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden; "Show" implies a read-only inspection, but that is never stated explicitly, nor is whether socket discovery probes or mutates anything. It does at least disclose the kind of data returned (manifest paths and socket discovery), which is useful for a no-annotation tool.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though extremely terse for a tool whose purpose overlaps a sibling.

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?

With no output schema, the description usefully names the two categories of information returned, which is the minimum needed. It remains incomplete about when to prefer it over chrome_bridge_status and whether the discovery step has side effects.

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 the baseline applies; there is nothing for the description to disambiguate. The listed subjects (manifest paths, sockets) correctly frame what is inspected.

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 gives a specific verb ("Show") and two concrete resources (native host manifest paths, discovered bridge sockets), so an agent can tell this is a diagnostics/introspection tool. It does not, however, differentiate itself from the similarly named sibling chrome_bridge_status, leaving real ambiguity about which status tool to pick.

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 alternatives such as chrome_bridge_status or chrome_get_info, and no prerequisites or context are given. The agent must infer usage from the word "Show" alone.

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