Skip to main content
Glama

move_nat_rule

Idempotent

Reposition a NAT rule within its chain to a specified 0-based index, letting you control the order in which firewall NAT rules are evaluated.

Instructions

Moves a NAT rule to a different position in the chain.

Notes: rule_id: use the ID from list output e.g. "*1" or "0" destination: 0-based target position index

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": {
      "rule_id": "<rule_id>",
      "destination": "<destination>"
    },
    "name": "move_nat_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNo
rule_idYes
destinationYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.14.5
    • addedInput schema / properties / device
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Device"
      +}
  2. First observedv0.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful operational detail beyond that — the rule_id format quirk ('*1' vs '0') taken from list output and the 0-based index semantics — but says nothing about what happens on out-of-range destinations, whether existing rules shift, or the impact on active traffic.

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?

The primary action is front-loaded in a single sentence, and the notes are short and without filler. The indented 'Notes:' layout is slightly awkward but costs nothing in comprehension.

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 simple repositioning tool with an output schema present, the definition covers the essentials plus the non-obvious ID format. It falls short of fully complete by omitting the device parameter and any failure or boundary behavior for destination indices.

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 0%, so the description must carry the parameter burden. It does add real meaning for rule_id (concrete example formats and the source being list output) and for destination (0-based target index), which the schema does not convey, but the third parameter 'device' is never mentioned, leaving a gap.

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 opens with a concrete verb and resource ('Moves a NAT rule') plus the precise effect ('to a different position in the chain'), which is meaningfully more specific than the name alone. It does not explicitly contrast with move_filter_rule or move_raw_rule, but the NAT scoping in the name and text is unambiguous enough for an agent to route correctly.

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 statement of when to use this versus update_nat_rule or create/remove_nat_rule, and no prerequisites or caveats about reordering firewall rules. The 'Notes' block explains parameter conventions rather than usage conditions, so guidance remains implicit.

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