Skip to main content
Glama
Sign In
hetzner-mcp

hetzner-mcp

by monk24215
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Capabilities

hz_capabilities
Read-onlyIdempotent

Shows which Hetzner modules are enabled, what they point at, and what to configure to turn the remaining ones on.

Instructions

Which modules are on, what they point at, and what to configure to switch the others on.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered without description help. The description adds content-level context about what the response covers (enabled modules, their targets, remediation config), which is useful, but it does not say whether the configuration guidance is advisory text or actionable data, and no output schema exists to clarify.

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?

A single front-loaded sentence with no filler, which suits a zero-argument introspection tool. It loses a point because the elliptical phrasing 'what they point at' is ambiguous and would read more clearly as an explicit verb-plus-object construction.

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

Completeness3/5

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

For a no-parameter, read-only tool with full annotation coverage, the bar is low and the description mostly clears it. However, with no output schema, the description is the only source of information about the return payload, and its three terse clauses leave the response shape and the nature of the configuration guidance underspecified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the schema has nothing to document and there is no parameter meaning for the description to add. Baseline 4 applies; nothing is missing or misleading on this dimension.

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

Purpose3/5

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

The description conveys the subject matter (module enablement state, what each module targets, and configuration needed to enable the rest) but never states a verb, so it is unclear whether the tool lists, reports, or diagnoses. The content does implicitly separate it from siblings like hz_host_list and hz_host_register, which concern hosts rather than modules, but an agent must infer that.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use statement, no preconditions, and no mention of alternatives among the sibling tools. The phrase 'what to configure to switch the others on' hints at a discovery/troubleshooting use case, but this is left for the agent to extrapolate rather than stated.

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