Skip to main content
Glama
Sign In
hetzner-mcp

hetzner-mcp

by monk24215
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Fleet overview

hz_fleet_overview
Read-onlyIdempotent

Get a consolidated overview of every server across configured Hetzner projects, including status, type, location, IP, backups, volumes, monthly gross cost, registry name, role, and protection.

Instructions

Every server in every configured Hetzner project: status, type, location, IP, backups, volumes, gross €/month, registry name and role, protection. Volume and traffic costs are not included in the total.

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_fleet_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely new behavioral context: the cross-project aggregation scope and the caveat that volume and traffic costs are excluded from the €/month total, which prevents misreading the cost figure. It stops short of describing result shape or ordering.

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 sentences, front-loaded with scope and field coverage, then a single targeted caveat. No redundant or filler wording; every clause carries information an agent needs.

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 no output schema, the description carries the burden of describing return content, and it does so by enumerating the fields returned plus the cost caveat. Minor gaps remain — whether results are grouped by project, ordering, and behavior when no projects are configured — but nothing critical to invoking a zero-parameter read tool is missing.

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 there is nothing for the description to disambiguate and the baseline of 4 applies. The field list in the description is return-value information rather than parameter semantics.

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?

The description states the resource and scope precisely — every server across every configured Hetzner project — and enumerates the attributes returned (status, type, location, IP, backups, volumes, cost, protection). The verb is implied rather than stated and there is no explicit contrast with the sibling hz_host_list, but an agent can still tell this is a fleet-wide aggregate rather than a filtered list.

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 guidance on when to call this versus hz_host_list or hz_capabilities, and no preconditions (e.g. requiring configured projects/credentials). The 'every configured project' phrasing hints at scope but does not route the agent between alternatives.

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