Skip to main content
Glama

login

Checks Perplexity.ai authentication for the default or specified browser profile and opens a visible window for one-time sign-in when needed.

Instructions

Check if you are authenticated on Perplexity.ai for the default or specified browser profile. If not, opens a visible browser window so you can log in once.

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": "login"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileNoOptional browser profile name or directory path for isolated/concurrent execution (e.g. 'default', 'worker-2'). When omitted, automatically routes to an idle slot in PERPLEXITY_PROFILE_DIRS / default profile.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.0

TDQS

A3.7/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 burden and does disclose the most consequential behavior: an unauthenticated state opens a visible browser window requiring a one-time human login. That is exactly the kind of side effect annotations would normally cover. It still omits timeout behavior, what happens in environments without a display, and whether the call blocks until login completes.

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, and the primary condition (check auth) is front-loaded before the fallback behavior. Nothing needs trimming and nothing important is buried.

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?

There is no output schema, so the description should state what the check returns (a boolean status, an error, or a login-required signal) and whether the call blocks while the user logs in. For a low-complexity single-optional-parameter tool the gaps are modest, but the return contract is left entirely to inference.

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% and the single profile parameter is fully documented in the schema, so the baseline is 3. The description reinforces the 'default or specified browser profile' framing but adds no routing details beyond what the schema already explains about idle slots and PERPLEXITY_PROFILE_DIRS.

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?

States a specific verb and resource: checks authentication state on Perplexity.ai for a browser profile, and opens a visible window if unauthenticated. This clearly distinguishes it from siblings like search, health_check, and list_models, though it never explicitly names or contrasts those alternatives.

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?

Implied usage is clear from the conditional: call it to verify auth, and if it fails you get a login window. However, it gives no explicit guidance on when to call it relative to other tools (e.g. before search), no mention of the health_check sibling, and no exclusions for headless or non-interactive environments.

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