Skip to main content
Glama
mcp-browserdata

mcp-browserdata

by igortetyuev

get_credentials

Retrieve saved passwords from installed browsers. Secrets stay masked by default; set reveal to true to view them, or pass a domain for Safari per-site lookup.

Instructions

Saved passwords. Passwords are masked unless reveal=True. Safari supports per-site lookup only — pass domain there.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "browser": "<browser>"
    },
    "name": "get_credentials"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainNo
revealNo
browserYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose two genuinely useful behavioral traits: passwords are masked by default and Safari only supports per-site lookup. It omits permissions/auth needs, what a masked value looks like, and any error behavior when a domain is missing for Safari.

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?

Two short sentences with the security-relevant masking rule front-loaded and zero filler. The fragment style and the ambiguous "there" in "pass domain there" cost it a point on clarity.

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?

For a credentialed-read tool with no annotations and 0% schema coverage, the masking and Safari caveats cover the riskiest gaps, and the existing output schema removes the need to describe return values. The undocumented required browser param still leaves an agent guessing how to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate and it partly does: it explains what reveal=True changes and constrains domain to Safari. The required browser parameter is never explained, nor are its valid values, leaving a third of the surface undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Saved passwords" names the resource but is a noun fragment with no explicit verb; the read/retrieve action is only inferred from the tool name. It is distinguishable from write-side siblings but never states it returns a list vs. a single credential.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The Safari note gives an operational rule (per-site lookup requires domain), which implies when the domain param must be supplied. There is no explicit when-to-use guidance and no mention of the obvious alternative, set_credential, for writing or updating entries.

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