Skip to main content
Glama
Sign In
hcloud-mcp

hcloud-mcp

by Xodus-CO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_load_balancer_metrics

Read-only

Retrieve Hetzner Cloud load balancer metrics for up to 30 days, with per-series min/avg/max/last summaries and optional raw time series for connections, requests, and bandwidth.

Instructions

Get load balancer metrics (last 30 days only). Output starts with a per-series summary {points,min,avg,max,last}, then the raw time_series unless include_values=false. Series: open_connections (number), connections_per_second, requests_per_second, bandwidth → bandwidth.in/bandwidth.out (bytes/s). Time range: pass start+end (ISO-8601), or omit both and use last_minutes (default 60)

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>",
      "type": "<type>"
    },
    "name": "get_load_balancer_metrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesLoad balancer ID
endNoPeriod end, ISO-8601/RFC3339. Give with start
stepNoResolution in seconds. Omit to let the API pick (~200 samples); the API caps at 500 samples and adjusts step to fit
typeYesMetric types, e.g. ["requests_per_second","bandwidth"]
startNoPeriod start, ISO-8601/RFC3339 (e.g. 2026-11-11T10:00:00Z). Give with end, or omit both and use last_minutes
last_minutesNoConvenience: period = now minus N minutes until now. Used only when start/end are omitted; default 60. Max 43200 (30-day retention)
include_valuesNoInclude the raw time series ([unix_ts, "value"] pairs) after the summary. Default true; set false for just the min/avg/max/last summary (much smaller output)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description only needs to add operational context — and it does: retention limit, default window, and that output leads with a per-series {points,min,avg,max,last} summary before raw points. It omits any mention of rate limiting, auth, or pagination behavior.

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?

Front-loaded with purpose and retention, then jumps into output shape and time-range semantics with no filler. The single dense paragraph is efficient, though the series/unit list could be slightly more scannable.

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 usefully describes the return structure and the meaning and units of each series, which is the main thing an agent needs. It stops short of covering the 'step'/sampling parameter, a minor gap given the schema already documents it.

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 parameters are already fully documented; the description reinforces the start/end-vs-last_minutes relationship and the include_values toggle but adds no new syntax or format detail. The 'step' parameter is never mentioned in the description.

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?

Opens with a specific verb+resource ('Get load balancer metrics') and immediately scopes it ('last 30 days only'), so an agent can tell this apart from get_server_metrics or the load balancer CRUD siblings without opening the schema.

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?

Gives concrete selection rules for the time parameters: 'pass start+end (ISO-8601), or omit both and use last_minutes (default 60)', plus the 30-day retention ceiling. It does not explicitly route callers away from an alternative tool, but the context is unambiguous.

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