Skip to main content
Glama
hcloud-mcp
by Xodus-CO

change_storage_box_subaccount_home_directory

Idempotent

Set or change a Storage Box subaccount's home directory; creates the target path when missing.

Instructions

Change a subaccount's home directory (created if missing). 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>",
      "home_directory": "<home_directory>"
    },
    "name": "change_storage_box_subaccount_home_directory"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesStorage Box ID
subaccount_idYesSubaccount ID
home_directoryYesHome directory relative to the main account root, e.g. "backups/app1". Created if missing

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 readOnly=false, destructive=false, idempotent=true and openWorld=true, so safety is covered structurally. The description adds real value beyond that by disclosing the async Action return and the required polling loop, plus the create-if-missing side effect. It stops short of describing failure behavior or whether existing data in the old directory is touched.

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 with zero filler; the core action is front-loaded and the follow-up polling instruction follows immediately. Every sentence carries distinct, actionable information.

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 three-parameter asynchronous mutation with no output schema, the description supplies the two things an agent most needs: the create-if-missing side effect and the polling contract. Minor gaps remain around error or failure statuses and conflicts with sibling update tools.

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 all three parameters are already documented, including the example path and the create-if-missing note. The description restates but does not extend that meaning, so the baseline of 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 ("Change a subaccount's home directory") with a useful side-effect qualifier ("created if missing"). It does not explicitly distinguish itself from the sibling update_storage_box_subaccount, so an agent must infer which mutation owns the home directory field.

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?

Provides clear operational guidance for the asynchronous flow: it returns an Action and the caller should poll get_storage_box_action until status is success. It gives no guidance on when to prefer this over update_storage_box_subaccount, nor any preconditions about the directory existing or permissions.

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