Skip to main content
Glama
dkruyt

Hetzner Cloud MCP Server

by dkruyt

reboot

Perform a soft reboot of a Hetzner Cloud server by gracefully shutting down and restarting it using the server ID.

Instructions

Reboot a server.

Performs a soft reboot (graceful shutdown and restart) of the server.

Example:
- Reboot server: {"server_id": 12345}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'reboot' tool. It takes a server ID, retrieves the server using the Hetzner Cloud client, and initiates a reboot action.
    def reboot(params: ServerIdParam) -> Dict[str, Any]:
        """
        Reboot a server.
        
        Performs a soft reboot (graceful shutdown and restart) of the server.
        
        Example:
        - Reboot server: {"server_id": 12345}
        """
        try:
            server = client.servers.get_by_id(params.server_id)
            if not server:
                return {"error": f"Server with ID {params.server_id} not found"}
                
            action = client.servers.reboot(server)
            
            # Don't wait for the action to complete - the method doesn't exist
            return {
                "success": True,
                "action": {
                    "id": action.id,
                    "status": action.status,
                    "command": action.command,
                    "progress": action.progress,
                    "error": action.error,
                    "started": action.started.isoformat() if action.started else None,
                    "finished": action.finished.isoformat() if action.finished else None,
                } if action else None,
            }
        except Exception as e:
            return {"error": f"Failed to reboot server: {str(e)}"}
  • Pydantic BaseModel defining the input schema for the 'reboot' tool, requiring a server_id integer.
    class ServerIdParam(BaseModel):
        server_id: int = Field(..., description="The ID of the server")
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It successfully communicates this is a mutation operation (reboot), specifies the type of reboot (soft/graceful), and provides an example. It doesn't mention potential side effects, permissions needed, or time estimates, but covers the core behavioral trait adequately.

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?

The description is perfectly structured: a clear purpose statement first, followed by important behavioral detail, then a practical example. Every sentence earns its place with zero wasted words, making it easy to scan and understand quickly.

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 mutation tool with no annotations, 0% schema coverage, but with an output schema present, the description does well. It covers purpose, behavior type, and provides an example. The output schema existence means return values don't need explanation. It could benefit from mentioning potential impacts or prerequisites for completeness.

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 0%, so the description must compensate. It provides an example showing the server_id parameter usage, which adds meaningful context beyond the bare schema. However, it doesn't explain parameter constraints, valid ranges, or where to find server IDs, leaving some gaps in parameter understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('reboot') and target resource ('a server'), distinguishing it from sibling tools like power_on/power_off. It provides a complete verb+resource statement that leaves no ambiguity about what this tool does.

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 provides clear context by specifying it performs a 'soft reboot (graceful shutdown and restart)', which helps differentiate it from hard resets or power cycling. However, it doesn't explicitly state when to use this versus alternatives like power_off/power_on or mention prerequisites like server state requirements.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dkruyt/mcp-hetzner'

If you have feedback or need assistance with the MCP directory API, please join our Discord server