Skip to main content
Glama
mcp-browserdata

mcp-browserdata

by igortetyuev

list_browsers

Detects installed browsers and reports profile paths, running state, CDP/file access, and read/write capabilities, helping you verify where browser data can be accessed or changed.

Instructions

Detected browsers: profile paths, running state, CDP/file access and per-kind capabilities (read/write flags).

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_browsers"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does disclose substantive behavior: it reveals that the result includes running state, CDP/file access mode, and per-kind read/write flags, which tells the agent what capabilities a detected browser exposes. It stops short of stating whether detection is a live scan versus reading persisted state, or whether the call has any cost.

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 compact sentence with the resource label front-loaded and no filler. It is telegraphic rather than fully grammatical, but every clause contributes information and nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is trivial to invoke (no inputs) and an output schema exists, so the description only needs to characterize the payload, which it does. The one residual gap is whether 'detected' means a live probe or a cached/static registry read, which affects how the agent should interpret the results.

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 there is nothing for the description to disambiguate beyond the schema. Baseline applies and the description adds the extra value of framing what the caller will receive.

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 names the resource ('Detected browsers') and enumerates exactly what the listing surfaces: profile paths, running state, CDP/file access, and per-kind read/write capability flags. It is not a verb-first statement, but the scope is unambiguous and no sibling in the catalog covers browser discovery, so an agent can distinguish it easily.

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 when-to-use guidance: nothing says this is the discovery step that should precede cookie/credential/state operations, and no exclusions or alternatives are given. The context of use is only inferable from the listed content.

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