Skip to main content
Glama
mcp-browserdata

mcp-browserdata

by igortetyuev

set_credential

Writes a single login/password credential for a specified browser and origin only when you explicitly request it, enabling targeted credential updates without bulk changes.

Instructions

Write one login/password. ONLY on explicit user request.

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>",
      "origin": "<origin>",
      "username": "<username>",
      "password": "<password>"
    },
    "name": "set_credential"
  }
}

Input Schema

NameRequiredDescriptionDefault
originYes
browserYes
passwordYes
usernameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden for a credential mutation. It reveals only two things: one credential per call, and that a user must ask. It is silent on whether an existing credential for the same origin/browser is overwritten or whether the write fails, whether any confirmation or elevated permission is required, and how secrets are handled.

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 zero wasted words, and the critical constraint is front-loaded. The brevity is close to under-specification for a secret-writing tool rather than genuine efficiency, which keeps it off a 5.

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?

An output schema exists, so return values need no explanation here, and the input names are largely self-describing. The one real gap is overwrite-versus-fail behavior, which is arguably out of scope for a description of this length. For a simple write tool, this level of detail is sufficient.

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

Parameters2/5

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

All four parameters (browser, origin, username, password) have 0% schema coverage, and the description explains none of them. 'origin' in particular is ambiguous without a format hint (full URL versus scheme plus host), and the browser parameter's expected identifier form is only guessable from the sibling list_browsers. The names being largely self-describing keeps this above a 1.

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 a specific verb and resource: 'Write one login/password.' An agent can tell this stores a single credential rather than reading credentials (get_credentials) or writing cookies/site storage (set_cookies, set_site_storage). It stops short of naming a sibling or the boundary explicitly, so it is clear but not fully differentiated.

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?

'ONLY on explicit user request' gives a hard precondition for invoking the tool and implies it should not be called autonomously or speculatively. It is a genuine usage constraint, but it names no alternative path and says nothing about prerequisites such as whether a browser session must exist first.

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