Skip to main content
Glama
Sign In
hcloud-mcp

hcloud-mcp

by Xodus-CO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

delete_network_route

DestructiveIdempotent

Remove a route from a Hetzner Cloud network by specifying the network ID, destination CIDR, and gateway IP; destination and gateway must exactly match the existing route.

Instructions

Delete a route from a network. destination and gateway must match the existing route exactly (see get_network routes). Returns an Action

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>",
      "destination": "<destination>",
      "gateway": "<gateway>"
    },
    "name": "delete_network_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesNetwork ID
gatewayYesGateway IP of the route
destinationYesDestination CIDR of the route

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so safety is covered structurally. The description adds real behavior beyond that: deletion requires exact-match identifiers, so a stale destination/gateway will not delete anything, and it discloses the return type (Action).

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?

Three short sentences with no filler: action first, then the exact-match constraint, then the return type. Nothing is buried and nothing is repeated from the schema.

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 full schema coverage, rich annotations, and no output schema, the only remaining gap is that 'Returns an Action' is not explained. The essential calling information, including the prerequisite lookup of existing routes, is present.

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?

Schema coverage is 100%, so the baseline would be 3. The description earns above baseline by imposing a semantic constraint the schema does not state: both destination and gateway are matching keys against an existing route, not free-form new values, which changes how the caller must populate them.

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?

States a specific verb and resource: delete a route from a network. Combined with the named fields (destination, gateway), an agent can distinguish this from delete_network, delete_network_subnet, and add_network_route without opening any 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 a concrete precondition: destination and gateway must match the existing route exactly, and routes the agent to get_network to look those up first. It does not state explicit when-not-to-use cases (e.g. against a route that does not exist), but the operational context is clear.

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