Skip to main content
Glama
Sign In
hcloud-mcp

hcloud-mcp

by Xodus-CO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_storage_box_actions

Read-only

List Storage Box actions across all boxes or a specific box, with optional filters for action IDs and status plus sorting. Use it to review running, successful, or failed Storage Box operations.

Instructions

List Actions (all pages). With storage_box_id: actions for that box. Without: actions across all Storage Boxes (optionally filtered by id)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_storage_box_actions"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoFilter by action IDs (Storage-Box-wide listing)
sortNoSort fields with optional direction, e.g. ["name:asc", "created:desc"]
statusNoFilter by status
storage_box_idNoStorage Box ID

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?

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered by structured data. The description adds a genuinely new behavioral trait, "all pages," telling the agent the call auto-paginates rather than returning a bounded page — consistent with the schema's lack of limit/page parameters — which implies potentially large result sets.

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 compact clauses with the scope decision front-loaded and no filler. The parenthetical "(optionally filtered by id)" is the only slightly muddy phrase, since its referent is unclear on first read.

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

Completeness5/5

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

For a read-only, four-optional-parameter listing tool with no output schema and full schema coverage, the description supplies the two things structured fields cannot: the scoping rule and the all-pages behavior. Nothing needed to invoke it correctly is missing.

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%, so the schema already explains id, sort, status and storage_box_id; the baseline of 3 applies. The phrase "optionally filtered by id" adds little and is slightly ambiguous about whether it means action IDs or storage box IDs, which the schema resolves but the description does not.

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?

"List Actions" gives a specific verb plus resource, and the two-mode breakdown (scoped to a storage box vs. across all boxes) makes the scope unambiguous. It stops short of naming the generic sibling list_actions, so an agent must infer which listing tool covers non-storage-box actions.

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?

The description states the selection condition explicitly: supply storage_box_id for one box's actions, omit it for a cross-box listing. It offers clear positive context but no exclusions or pointer to get_storage_box_action for fetching a single action.

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