Skip to main content
Glama

Sign Out of Varity

varity_logout
DestructiveIdempotent

Signs this computer out of Varity by revoking the saved sign-in everywhere and removing it locally. Use when the user asks to sign out or disconnect.

Instructions

Sign this computer out of Varity: the saved sign-in is revoked on Varity, so it stops working everywhere, then removed from this computer. Use only when the user asks to sign out or disconnect. A key set in the MCP server environment is not changed.

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_logout"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.0.1

TDQS

A4.7/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: the sign-in is revoked server-side so it 'stops working everywhere', then removed from this computer, and an environment-configured key is explicitly untouched. That blast-radius and exception disclosure is exactly the kind of context destructiveHint=true alone cannot convey.

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?

Three short sentences, front-loaded with the action and its consequence, then the usage gate, then the one caveat an agent would otherwise get wrong. No filler.

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?

Zero parameters, no output schema, and annotations already cover safety and idempotency; the description covers what remains (scope, side effect, local-only exception, when to invoke). Nothing an agent needs in order to call it correctly is missing.

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?

The tool takes no parameters, so there is no parameter meaning to add; the description correctly says nothing about inputs and instead spends its words on effects. Baseline 4 applies for a zero-parameter tool.

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 scope: 'Sign this computer out of Varity', and immediately explains what that means concretely (revoked on Varity, removed locally). An agent can distinguish this from varity_login 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 an explicit usage gate: 'Use only when the user asks to sign out or disconnect.' It does not name the counterpart tool (varity_login) or state what to do instead when the user has not asked, but the invocation condition is unambiguous.

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