Skip to main content
Glama
Sign In
hcloud-mcp

hcloud-mcp

by Xodus-CO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

update_storage_box_access_settings

DestructiveIdempotent

Update a storage box's main account access settings, such as SSH, Samba, WebDAV, ZFS, and external reachability; omitted fields remain unchanged. Returns an action to poll until complete.

Instructions

Update the main account's access settings (partial: omitted fields are unchanged). 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>"
    },
    "name": "update_storage_box_access_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesStorage Box ID
ssh_enabledNoEnable SSH/SFTP/SCP (port 23)
zfs_enabledNoShow the .zfs snapshot folder
samba_enabledNoEnable Samba/SMB
webdav_enabledNoEnable WebDAV
reachable_externallyNoAllow access from outside the Hetzner network

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A4/5.0
Behavior4/5

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

Adds real behavior beyond annotations: partial-update semantics and the asynchronous Action-plus-polling workflow, neither of which is expressible in the hints. Given destructiveHint=true, it does not warn that disabling channels (e.g. SSH, Samba, external reachability) can lock out users, which is the one meaningful gap.

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, front-loaded with the action and its scope, then the partial-update guarantee and the follow-up step. No filler whatsoever.

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?

With schema fully documented and no output schema, the description supplies what the schema cannot: partial-update behavior and the returned Action with its polling protocol. Only the destructive consequences of toggling channels off are left unstated.

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 each flag is already documented in the schema, setting the baseline at 3. The description does add the crucial partial-update rule (omitted fields unchanged), which applies to all five optional booleans, but it does not clarify defaults or the effect of setting a flag to false.

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 — updating the main account's storage box access settings — and the word "main" implicitly separates it from the subaccount sibling. It also declares the return type (Action), though it never names the subaccount variant explicitly as an alternative.

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 clear operational context: omitted fields are left unchanged (partial update) and the caller must poll get_storage_box_action until status is success. It stops short of stating when to prefer this over update_storage_box_subaccount_access_settings, leaving that routing to 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