MikroTik MCP

move_filter_rule

Idempotent

Rearranges firewall filter rules by moving a rule to a new position in the chain. Specify the rule ID and target index to reorder rules for correct traffic processing.

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

Input Schema

TableJSON Schema

Name	Required	Description	Default
`device`	No
`rule_id`	Yes
`destination`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.14.5Aug 10, 2026

addedInput schema / properties / device

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Device"
+}

First observedv0.0.0Aug 8, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, so the safety profile is clear. The description adds no new behavioral facts beyond the reorder semantics, and it does not contradict the annotations. It also does not disclose edge-case behavior such as moving to the current position or effects on traffic ordering.

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 description is compact and front-loaded: one clear action sentence followed by two focused parameter notes. Every sentence adds useful information and there is no filler.

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?

Given the simplicity of the operation, the annotations, and the presence of an output schema, the description is nearly complete. It clearly explains the two critical inputs. It would be more complete if it explicitly told the agent to obtain rule_id via list_filter_rules and described invalid destination behavior.

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 has to compensate. It does so well for the two required parameters: rule_id is clarified as being either a positional number or an internal ID, and destination is explicitly documented as 0-based. Only the optional device parameter is left undocumented, but its optionality and default are visible in the schema.

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?

The description opens with a specific verb and resource: 'Moves a firewall filter rule to a different position in the chain.' This clearly states what the tool does and distinguishes it from sibling tools like move_nat_rule and move_ipv6_filter_rule by naming the firewall filter rule resource.

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 explicit guidance is given on when to use this tool versus alternatives. The only usage hint is that rule_id comes 'from list output', implying list_filter_rules should be called first, but there is no clear when-to-use or when-not-to-use guidance relative to sibling move tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server