Skip to main content
Glama
mienetic

Ghostvault

by mienetic

Create Custom Provider

gv_create_provider
Destructive

Create a custom login provider recipe for any website. Define login URL, success indicators, and auth cookies to enable automated account creation and sign-in.

Instructions

Create a custom login provider recipe for any website.

Once created, use it with gv_create_account(provider=name) or gv_sign_in(account_id, provider=name). The provider recipe is stored in ~/.ghostvault/providers.json and shared across all accounts.

Args: name: Unique provider name (e.g. "my_bank"). Cannot shadow built-ins. login_url: The URL to navigate to for login (e.g. "https://app.example.com/login"). success_url_fragments: URL fragments indicating login succeeded (e.g. ["app.example.com/dashboard"]). auth_cookie_names: Cookie names that prove authentication (e.g. ["session_id"]). auth_cookie_domain: The domain to read auth cookies from (e.g. "https://app.example.com"). logout_url: Optional direct logout URL. If None, user must logout manually. session_probe_url: Optional URL to check if session is still valid. login_url_fragments: URL fragments indicating redirect to login (session expired). description: Human-readable description of this provider.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
login_urlYes
logout_urlNo
descriptionNo
auth_cookie_namesYes
session_probe_urlNo
auth_cookie_domainYes
login_url_fragmentsNo
success_url_fragmentsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Annotations indicate 'destructiveHint: true', and description does not contradict. Adds context about persistent storage in ~/.ghostvault/providers.json and sharing across accounts, but lacks details on potential conflicts or error conditions.

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?

Description is well-structured with clear front-loaded purpose and organized Args section. Code snippets are helpful; slightly verbose but each sentence adds value.

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?

Given 9 parameters and 5 required, description covers all parameters and explains their roles. References output schema exists, so return values not needed. Mentions storage and usage across accounts, making it complete.

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?

Schema description coverage is 0%, but the description provides detailed parameter explanations, including optional ones with defaults, adding critical meaning beyond the schema structure.

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?

Specific verb 'Create' and resource 'custom login provider recipe'. Distinguishes from siblings like gv_delete_provider and gv_get_provider by stating it's for creation. Includes important constraint 'Cannot shadow built-ins.'

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?

Explicitly states how to use the created provider with gv_create_account and gv_sign_in, providing context. Mentions storage location but does not explicitly state when not to use this tool versus alternatives.

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