Skip to main content
Glama

Reset VPS root password

vps_reset_password
Destructive

Generate a new root password for a VPS. Returns the new password, which then sits in this conversation. You MUST set confirm to true.

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>",
      "confirm": "<confirm>"
    },
    "name": "vps_reset_password"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe VPS ID
confirmYesMust be true to confirm this destructive operation

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds genuine value by disclosing that the new password is returned and persists in the conversation, which is a real security consideration, but it omits whether existing sessions/keys are invalidated and whether the old password stops working immediately.

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?

Three short sentences with the core action front-loaded and no filler; the exposure warning earns its place. The trailing 'You MUST set confirm to true' is somewhat redundant with the schema, slightly reducing efficiency.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description does cover the key return behavior (the new password is surfaced in-conversation), which is the main thing an agent needs. However, for a destructive credential-mutating tool it leaves gaps around side effects and alternatives that a richer definition would address.

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%, so both parameters are already documented, and the description's 'You MUST set confirm to true' largely restates the schema's own 'Must be true to confirm this destructive operation'. The 'id' parameter receives no additional meaning from the description. Baseline 3 applies.

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?

States a specific verb and resource: 'Generate a new root password for a VPS.' An agent can distinguish this from vps_set_password_auth or webspace_reset_db_password by the word 'reset'/'new' plus the root scope, though the description never names those siblings to make the contrast explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to choose this over vps_set_password_auth or vps_rescue_password_auth, and no stated prerequisites such as the VPS needing to be running or the caller needing ownership. The only instruction is the confirm=true requirement, which is a parameter constraint rather than usage guidance.

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.