Skip to main content
Glama
Sign In
hcloud-mcp

hcloud-mcp

by Xodus-CO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

reset_storage_box_password

DestructiveIdempotent

Sets a new password for a Storage Box main account, invalidating existing clients that use the old password; returns an action to poll until completion.

Instructions

Set a new password for the Storage Box main account (existing clients using the old password lose access). Returns an Action; poll get_storage_box_action until status is success

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>",
      "password": "<password>"
    },
    "name": "reset_storage_box_password"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesStorage Box ID
passwordYesPassword policy: 12-128 chars from a-z A-Z ÄÖÜäöüß 0-9 ^°!§$%/()=?+#-.,;:~*@{}_& with at least one upper case letter, lower case letter, digit and special character; must not appear in known data breaches. Generate a strong random one; never echo it back to the user unless they asked for it

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, yet the description still adds meaningful context: existing clients using the old password lose access. That consequence is exactly what an agent needs before committing to a destructive change, and the async Action/polling pattern is disclosed too. Missing are any permission or rate-limit notes.

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 tight sentences with no filler: the destructive consequence is front-loaded in parentheses and the follow-up polling step comes last. Every clause earns its place.

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 destructive two-parameter mutation with no output schema, the description covers the impact on existing clients and points to the follow-up tool needed to confirm success. It does not describe what the returned Action contains, but naming get_storage_box_action largely covers that gap.

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 the password policy, length bounds, and Storage Box ID semantics are fully documented in the schema itself. The description adds no parameter-level meaning beyond that, so the 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?

The description gives a specific verb and resource ("Set a new password for the Storage Box main account") and the qualifier "main account" implicitly separates it from the subaccount password sibling. It stops short of naming that sibling explicitly, so an agent must infer the distinction.

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?

It tells the agent what to do after the call (poll get_storage_box_action until status is success), which is genuine procedural guidance. It does not say when to choose this over reset_storage_box_subaccount_password or reset_root_password, so the choice is only implied by the word "main".

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

Deploy Server

Other Tools