Skip to main content
Glama
Sign In
hcloud-mcp

hcloud-mcp

by Xodus-CO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

request_console

Requests time-limited VNC-over-websocket console credentials for a Hetzner Cloud server, returning a secret wss_url and VNC password to access keyboard, monitor, and mouse.

Instructions

Request VNC-over-websocket console credentials (keyboard, monitor, mouse) for a server. Returns wss_url (contains a token) and a VNC password, plus an Action. The URL must be used to connect within 1 minute; request a new one after that. An already-open connection is not cut off by that timeout. Treat both values as secrets

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": "request_console"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesServer ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A4.4/5.0
Behavior5/5

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

With annotations only saying this is not read-only, not idempotent, non-destructive but open-world, the description carries real weight: it names the returned fields (wss_url containing a token, a VNC password, an Action), the 1-minute expiry, the survival of existing sessions past that expiry, and a secrecy obligation on both values. That is exactly the kind of context annotations cannot express.

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?

Sentences are packed with actionable detail and the return-value information comes early, ahead of the timeout constraint. The only rough spot is the fragment 'plus an Action' and the trailing unpunctuated 'Treat both values as secrets', which read as compression rather than crafted sentences, though no content is wasted.

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?

There is no output schema, so the description's coverage of return fields, the credential expiry rule, and the secrecy requirement fills the gap completely for a one-parameter tool. An agent knows what it will get back, how long it is valid, and how to handle the values.

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?

There is a single parameter, id, and schema coverage is 100% with 'Server ID' documented in the schema. The description only implies the parameter by saying 'for a server' and adds no ID format, source, or resolution guidance, so the baseline of 3 applies.

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 states a specific verb and resource: 'Request VNC-over-websocket console credentials (keyboard, monitor, mouse) for a server.' The protocol detail and the parenthetical that expands the acronym make the deliverable unambiguous, and no sibling tool in the catalog offers console access, so mis-selection risk is low.

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?

It gives an explicit operational window ('must be used to connect within 1 minute; request a new one after that') and clarifies a non-obvious edge case: an already-open connection survives the timeout. What it lacks is any statement of preconditions or exclusion, such as whether the server must be in a particular power state or whether a console session should be preferred over other access methods.

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