Skip to main content
Glama
Sign In
hcloud-mcp

hcloud-mcp

by Xodus-CO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

reset_storage_box_subaccount_password

DestructiveIdempotent

Reset a Storage Box subaccount password to rotate credentials; returns an action to poll until the change succeeds.

Instructions

Set a new password for a subaccount. 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>",
      "subaccount_id": "<subaccount_id>",
      "password": "<password>"
    },
    "name": "reset_storage_box_subaccount_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
subaccount_idYesSubaccount ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the mutation profile is covered. The description's meaningful addition is the asynchronous execution model and the named polling tool, which the annotations do not convey. It does not say what happens to existing sessions or credentials when the password changes, and the missing-null title gives no extra context.

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?

Two sentences, front-loaded with the action and immediately followed by the required post-call flow. No filler, though the polling sentence is terse to the point of omitting the returned action identifier's name.

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, idempotent async mutation tool with no output schema, the description covers the essential gap: the call returns an Action and completion must be confirmed via get_storage_box_action. It stops short of stating irreversibility or session-invalidation effects, which would round out a destructive operation.

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 description coverage is 100%, and the password property already embeds the full policy text plus generation guidance, so the schema carries all parameter meaning. The description adds nothing about the id/subaccount_id pairing or password constraints. Baseline 3 is appropriate.

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: 'Set a new password for a subaccount.' The 'subaccount' qualifier does most of the work distinguishing it from reset_storage_box_password and reset_root_password, but the description never names those siblings, so the differentiation is implicit rather than explicit.

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?

The follow-up workflow is spelled out ('poll get_storage_box_action until status is success'), which is real operational guidance. However, there is no statement about when to choose this over reset_password or reset_root_password, nor any mention of prerequisites such as permissions or the caller's authority over the subaccount.

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