Skip to main content
Glama

Set Up Varity Login

varity_login
Idempotent

Checks whether a Varity deploy key is configured and opens the developer portal settings page when login is needed, so you can authenticate before deploying.

Instructions

Check whether a deploy key is already configured and open the developer portal settings page when login is needed. Credentials are never accepted as MCP tool input; set VARITY_DEPLOY_KEY in the MCP server environment, or enter the deploy key only in the hidden prompt of varitykit auth login in a trusted terminal, which saves it to ~/.varitykit/config.json.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.0
    • removedInput schema / properties / deploy_key
      Removed value: -{
      -  "description": "Your deploy key from the Varity developer portal (developer.store.varity.so/dashboard/settings). If omitted, this tool opens the settings page in your browser, copy your key from there, then call varity_login again with the key.",
      -  "type": "string"
      -}
  2. First observedv2.0.0-beta.24

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, idempotent=true, destructive=false), the description discloses that no credentials are accepted as tool input, that the tool may open a browser page, and where keys persist (~/.varitykit/config.json). This is genuinely useful behavioral context an agent could not infer from the annotations. It does not describe what happens on failure or whether opening the portal has side effects, leaving a small gap.

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?

Two sentences, front-loaded with the action, followed by the credential-handling constraint. The second sentence is dense with paths and command syntax, but every clause carries actionable information; no filler is present.

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 zero-parameter, no-output-schema tool the description covers the full flow: detect missing key, open the portal, and how to install the key out-of-band. The only omission is post-call behavior on failure or when a key is already configured, which is minor given the simplicity of the tool.

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

Parameters4/5

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

There are zero input parameters, so the baseline is 4 and there is no parameter meaning to add. The description correctly reinforces that no credential argument exists, which prevents an agent from attempting to pass one.

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?

The description names concrete actions: check whether a deploy key is configured, and open the developer portal settings page when login is needed. That is far more specific than the name 'varity_login' alone and is distinguishable from siblings like varity_open_browser or varity_set_env. It does not explicitly contrast itself with those siblings, which keeps it short of a 5.

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?

It states the triggering condition ('when login is needed') and gives concrete alternatives for supplying credentials: the VARITY_DEPLOY_KEY environment variable or the hidden prompt of `varitykit auth login`. It stops short of saying when not to call the tool (e.g. if a deploy key is already present, the check presumably suffices), so no explicit exclusion is given.

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