Skip to main content
Glama

move_filter_rule

Idempotent

Reposition a firewall filter rule within its chain by specifying the rule ID and target 0-based destination index to reorder filtering priority.

Instructions

Moves a firewall filter rule to a different position in the chain.

Notes: rule_id: positional number from list output (e.g. "12") or internal ID (e.g. "*1A") 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_filter_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

A3.7/5.0
Behavior3/5

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

Annotations already state readOnlyHint=false, destructiveHint=false and idempotentHint=true, so the agent knows this is a safe, repeatable mutation. The description confirms the operation reorders within a chain but does not say whether other rules' positions shift, whether the move affects any rule indices returned earlier, or whether it persists across reboots — context that matters for a mutation on this device type.

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?

The purpose sentence is front-loaded, followed by a compact notes block that gives exactly two pieces of non-obvious format information. There is no filler or repetition of schema structure.

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?

An output schema exists, so return values need not be described, and annotations cover the safety profile. What remains missing is the undocumented 'device' parameter and any note about ordering side effects, but for a three-parameter repositioning tool the definition is nearly sufficient.

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 description coverage is 0%, so the description must carry the load, and it does for the two required parameters: rule_id's two accepted forms (positional number vs '*1A'-style internal ID) and destination's 0-based index. The optional 'device' parameter is left unexplained, which is the main 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 gives a specific verb and resource — 'Moves a firewall filter rule to a different position in the chain' — which distinguishes it from create/enable/disable/remove siblings. It does not explicitly distinguish reordering from update_filter_rule or move_nat_rule/raw_rule variants, so the differentiation is only implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The note that rule_id is a 'positional number from list output' implies the prerequisite step (list_filter_rules) and where the identifier comes from. There is no explicit when-to-use/when-not guidance or named alternative for editing a rule rather than repositioning it.

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