Skip to main content
Glama
mienetic

Ghostvault

by mienetic

Sign In to Provider

gv_sign_in

Open a sign-in window for user to complete login and 2FA. Supports auto-fill with stored credentials or manual entry for SSO providers.

Instructions

Open a sign-in window for the user to complete login (including 2FA).

A real browser window opens on the server's machine — the USER completes sign-in themselves; Ghostvault never touches the password. On success the session is saved to the account's persistent profile automatically.

First-time login from a new fingerprint usually triggers a 2FA challenge — this is expected. The tool blocks until login completes or times out.

Login level is auto-selected:

  • If the provider has login_steps AND credentials are available (either passed here or stored via gv_set_credentials) → Level 2 auto-fill.

  • Otherwise → Level 1 manual (user does everything in the visible window).

DECISION GUIDE:

  • For Google / SSO providers → Level 1 manual (most reliable for 2FA/captcha).

  • For providers with login_steps → store credentials first via gv_set_credentials, then sign_in.

  • Not sure what the page offers? Call gv_detect_login_options first.

Args: account_id: The account id from gv_list_accounts. provider: Override the provider for this login (e.g. "github", "facebook", or a custom provider name). Defaults to the account's provider field. credentials: Optional dict of credential values for Level 2 auto-fill (e.g. {"username": "john", "password": "secret"}). If omitted, stored credentials are loaded automatically.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
providerNo
account_idYes
credentialsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

The description adds extensive behavioral context beyond the annotations (only openWorldHint): it opens a real browser window, user completes sign-in without Ghostvault touching password, session saved automatically, blocks until completion or timeout, and auto-selects login level. No contradiction with annotations.

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?

The description is detailed and well-structured with paragraphs and a decision guide. Every sentence adds value, but it is somewhat lengthy. However, given the tool's complexity (two login levels, credential handling), the length is justified.

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?

The description covers key aspects: blocking behavior, auto-login level selection, credential handling, and reference to sibling tools. It lacks mention of the return value/response, but since an output schema exists (summary signals), this is partially mitigated. Overall, it is fairly complete for the tool's complexity.

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

Parameters5/5

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

Despite 0% schema description coverage, the description's Args section explains each parameter: account_id as required, provider with default behavior (defaults to account's provider), and credentials as optional with clear role in Level 2 auto-fill. This adds significant meaning beyond the schema's type-only definitions.

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?

The description clearly states the tool opens a sign-in window for user login including 2FA. It specifies the resource (sign-in window) and verb (open), and distinguishes from siblings like gv_detect_login_options and gv_set_credentials by explaining when to use each.

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?

The description provides explicit decision guidance: for Google/SSO use Level 1, for providers with login_steps store credentials first via gv_set_credentials, and if unsure call gv_detect_login_options. It also differentiates between Level 1 and Level 2 login based on credential availability, giving clear when-to-use and when-not-to-use advice.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mienetic/Ghostvault'

If you have feedback or need assistance with the MCP directory API, please join our Discord server