Skip to main content
Glama

screen_login

Idempotent

Open a window on the user's screen, in the recorded browser's own profile, for the USER to sign in to a site. Tell the user to sign in and close it, then screen_open the page again: the browser stays signed in. You never see what they type.

response_detail (summary|ids|compact|full), fields (dotted paths), cursor (next page) — see the server instructions.

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": {
      "url": "<url>"
    },
    "name": "screen_login"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
cursorNo
fieldsNo
response_detailNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only declare the safety profile (readOnly=false, idempotent, non-destructive); the description adds behavior the annotations cannot: a real window appears on the user's desktop, it uses the recorded browser profile, credentials never pass through the agent, and the resulting signed-in session persists across later calls. That is exactly the context needed to reason about side effects and privacy.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first paragraph is front-loaded and wastes nothing, walking through open, hand off, close, re-open. The trailing parameter sentence is a copy-paste fragment that does not read as belonging to this tool and dilutes an otherwise tight definition.

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?

The core human-in-the-loop flow is complete and annotations cover the safety profile, with no output schema needed. But the required url argument is left unexplained and the appended response_detail/fields/cursor text raises doubt about whether this tool paginates results, leaving real ambiguity for a moderate-complexity interaction tool.

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 carry parameter meaning, and it does explain response_detail with its enum values, fields as dotted paths, and cursor as next page. However, the required url parameter is never described, and those three pagination-style parameters look like boilerplate carried over from a listing tool, which makes their relevance to a login action unclear.

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 specific verb and resource: open a window on the user's screen, in the recorded browser's own profile, so the USER can sign in. It also distinguishes itself from the follow-up step by naming screen_open as what to call after the user finishes, so an agent can place it in the workflow without opening a schema.

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?

Gives a clear procedural when-to-use: call this when a site needs the human's credentials, instruct the user to sign in and close the window, then re-open the page with screen_open because the session persists. It does not contrast with screen_hand_over, the obvious alternative for handing control to the user, so the routing is clear but not exhaustive.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.