Skip to main content
Glama

Log in through Chrome

login
Read-only

Opens Chrome on a connector’s sign-in page and waits until the session is active, letting you authenticate ahead of session expiry.

Instructions

Open Chrome on a connector's login page and wait until its session works. Other tools already do this by themselves when they hit an expired session; use this to log in ahead of time.

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": {
      "instance": "<instance>"
    },
    "name": "login"
  }
}

Input Schema

NameRequiredDescriptionDefault
instanceYesConnector name (see list_connectors).
wait_secondsNoHow long to wait for the login (default from settings, 180).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations, the description discloses that a real Chrome browser is opened and that the call blocks until the session is usable — meaningful operational context an agent needs for scheduling. It does not cover what happens on timeout/failure or whether user interaction may be required, and there is mild tension with readOnlyHint=true since a login establishes session state, though nothing in the text directly contradicts the annotations.

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 sentences, zero waste, with the core action front-loaded and the usage caveat second. Every clause carries distinct information.

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?

For a simple two-parameter tool with annotations covering the safety profile and full schema coverage, the description supplies purpose, timing guidance, and blocking behavior. Only failure/timeout behavior and any interactivity requirements are left unstated, which is a minor gap rather than an obstacle to correct invocation.

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 100%, so both `instance` and `wait_seconds` (including its default) are already documented in the schema. The description only gestures at the waiting behavior and adds no format or syntax detail beyond structured fields, making the baseline score appropriate.

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?

States a concrete verb and resource: 'Open Chrome on a connector's login page and wait until its session works.' It also distinguishes itself from an implicit alternative behavior (other tools perform the login automatically on session expiry), so an agent can tell what this tool uniquely does without opening the schema.

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

Usage Guidelines5/5

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

Gives both sides of the decision: use it 'to log in ahead of time,' and it is unnecessary when another tool hits an expired session because those tools handle it themselves. That is an explicit when-to-use plus a when-not-to-use condition, which is exactly the guidance needed to avoid redundant calls.

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