Skip to main content
Glama

forget_password

Idempotent

Clear saved 5250 sign-on passwords from memory and the system keychain, optionally for a host or user, so the next sign-on prompts for credentials again.

Instructions

Forget saved passwords (kept after sign-ons that worked, in memory and, if the user chose so, in the system keychain). The next sign-on asks again.

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

Input Schema

NameRequiredDescriptionDefault
hostNoonly for this host
userNoonly for this user profile

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations, the description explains that saved passwords are kept in memory and optionally in the system keychain, and that the next sign-on will prompt again. This adds meaningful behavioral context about scope and reversibility. It does not contradict readOnlyHint=false or destructiveHint=false, since forgetting saved credentials is recoverable by signing on and saving again.

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?

The description is two tight sentences with the core action front-loaded and the parenthetical storage detail appropriately subordinate. No wording is wasted.

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 low-complexity tool with annotations and a full output schema, the description covers the important behavior: what saved passwords are, where they live, and what happens next. It is nearly complete, with the main gap being explicit routing or selection guidance.

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?

The schema has 100% description coverage for both optional parameters, so the baseline is 3. The description itself does not add further meaning about how host and user filter the operation, leaving that entirely to the schema.

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 states a specific verb and resource: forgetting saved passwords. It clarifies where those passwords are stored and the postcondition, but it does not explicitly distinguish this tool from related sign-on tools such as connect or disconnect.

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?

Usage is implied by the described effect, and 'The next sign-on asks again' gives useful context about when the tool is appropriate. However, it does not state explicit when-to-use or when-not-to-use guidance, nor does it name alternatives.

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