Skip to main content
Glama
Sign In
mcp-stealth-chrome

mcp-stealth-chrome

by RobithYusuf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_chrome_profiles

List all Chrome/Chromium/Edge/Brave profiles on the system by reading the browser's Local State JSON file. Returns profile name, email, path, in-use status, and existence.

Instructions

List all Chrome/Chromium/Edge/Brave profiles found on this system.

Reads browser 'Local State' JSON (read-only). Returns profile name, user email, path, whether in-use (Chrome currently running on it), and whether it exists.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.12

TDQS

A4.1/5.0
Behavior4/5

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

Description discloses read-only behavior (reads JSON), return fields, and that it checks if profile is in-use. Without annotations, it provides good transparency for a list operation, though could mention potential errors if browser not installed.

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?

Two concise sentences: first defines purpose, second adds technical detail. Front-loaded and no wasted words.

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 zero parameters and existence of output schema, description fully covers what the tool does and what it returns. Provides enough context for an AI agent to use it 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?

No parameters, so baseline 4. Description adds no parameter info needed. Schema coverage is 100% naturally.

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?

Description clearly states it lists browser profiles (Chrome/Chromium/Edge/Brave) from system, specifying the data source ('Local State' JSON) and return fields (name, email, path, in-use, existence). This is specific and distinguishes from sibling tools like list_external_chrome which list instances.

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 explicit guidance on when to use this tool vs alternatives like list_external_chrome or clone_chrome_profile. No mention of prerequisites or exclusions. Context is implied but not stated.

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