Skip to main content
Glama

Set SSH password login

vps_set_password_auth
Idempotent

Toggle SSH password authentication (PasswordAuthentication) in sshd_config. Use vps_rescue_password_auth when SSH is unreachable.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>",
      "enabled": "<enabled>"
    },
    "name": "vps_set_password_auth"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe VPS ID
enabledYesWhether to enable or disable the setting.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the description does not need to re-establish safety. It adds that the change lands in sshd_config, but says nothing about whether sshd is reloaded/restarted, whether the change takes effect immediately, or the lockout risk when disabling password auth — meaningful gaps for a config mutation.

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?

Two short sentences, front-loaded with the action and backed by a single alternative route. No filler, no restatement of the title.

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 two-parameter idempotent config toggle with full schema coverage and annotations, purpose and fallback routing are covered. The only real omission is post-change behavior (apply timing / sshd reload), which an operator would likely want before toggling password auth.

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?

Schema coverage is 100% and both parameters carry descriptions, so the schema does the heavy lifting. The description's parenthetical naming the underlying directive (PasswordAuthentication) adds a little mapping context, but does not extend the meaning of id or enabled beyond the schema.

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 action (toggle SSH password authentication) bound to a concrete resource (PasswordAuthentication in sshd_config), and explicitly names the sibling vps_rescue_password_auth as the different path. An agent can distinguish it from other SSH tools without opening the 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 routing condition: use vps_rescue_password_auth when SSH is unreachable, which clarifies this tool's operating context. It stops short of stating prerequisites for this tool itself (e.g. that SSH access or a specific auth mode is required to run it safely).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.