Skip to main content
Glama
lazyants

hetzner-mcp-server

by lazyants
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List Floating IP Actions

hetzner_list_floating_ip_actions
Read-onlyIdempotent

List all actions performed on a specific floating IP, including assign, unassign, and rDNS changes.

Instructions

List all actions performed on a specific floating IP, such as assign, unassign, and rDNS changes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesFloating IP ID
pageNoPage number
sortNoSort field, e.g. "id:asc" or "name:desc"; pass an array for multiple sort fields
statusNoFilter by action status: "running", "success", or "error"; pass an array for multiple statuses
per_pageNoResults per page (max 50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv3.0.0
    • addedInput schema / properties / sort / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+]
    • changedInput schema / properties / sort / description
      Previous value: -"Sort field, e.g. \"id:asc\" or \"name:desc\""New value: +"Sort field, e.g. \"id:asc\" or \"name:desc\"; pass an array for multiple sort fields"
    • removedInput schema / properties / sort / type
      Removed value: -"string"
    • addedInput schema / properties / status / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+]
    • changedInput schema / properties / status / description
      Previous value: -"Filter by action status: comma-separated list of \"running\", \"success\", \"error\""New value: +"Filter by action status: \"running\", \"success\", or \"error\"; pass an array for multiple statuses"
    • removedInput schema / properties / status / type
      Removed value: -"string"
  2. First observedv2.2.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is fully covered and the description carries a lower burden. The description adds that this is a historical action log and lists example action types, which is genuinely useful context. It does not mention pagination or result ordering, which are relevant given the page/per_page params.

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?

A single well-formed sentence with no wasted words, and the core purpose is front-loaded. The concrete action examples add clarity without bloat.

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 paginated read-only list tool whose annotations and full schema coverage already carry the safety and parameter burden, the description is nearly complete. It would be improved by noting pagination behavior, but nothing essential to invoking it correctly is missing.

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 the schema already documents id, page, per_page, sort, and status including enum-like values for status. The description adds no parameter semantics beyond what the schema provides; baseline 3 applies.

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?

States a specific verb (list) and resource (actions on a specific floating IP), then enumerates the kinds of actions (assign, unassign, rDNS changes). This distinguishes it from the sibling hetzner_list_floating_ips, which lists the IPs themselves rather than their history. It stops short of naming a sibling explicitly, so it lands just under 5.

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?

No guidance on when to use this tool versus alternatives such as hetzner_list_floating_ips or hetzner_get_floating_ip, and no stated prerequisites (e.g. that the floating IP id must already be known). Usage is only implied by the description. No exclusions or conditions are given.

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