Skip to main content
Glama

move_raw_rule

Idempotent

Reposition an /ip firewall raw rule on a MikroTik device by specifying its internal ID or print position and a 0-based destination index.

Instructions

Moves an /ip firewall raw rule to a different position.

Notes: rule_id: a RouterOS internal id ("*1A") or a print position ("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_raw_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNo
rule_idYes
destinationYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.28.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false), so the description only needs to add context. It adds the 0-based destination convention and the two rule_id forms, but says nothing about what happens to the displaced rules' positions or whether the move is transactional — useful gaps for a reordering mutation.

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?

Purpose is front-loaded in a single sentence and the notes are short and scannable. Slightly more structured labeling than needed for a two-line note block, but nothing is wasted.

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 three-parameter mutation tool with zero schema description coverage, the definition covers only two parameters and omits device entirely, plus no statement of what the call returns despite an output schema existing (that part is acceptable). Adequate but with a clear hole.

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 carries the burden, and it does explain rule_id (internal id like "*1A" or print position "0") and destination (0-based target index) — meaning the schema text does not provide. However the third parameter, device, is never mentioned anywhere, leaving one of three parameters fully undocumented.

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 (moves) and a precise resource path (/ip firewall raw rule) plus the effect (to a different position), which separates it from the ipv6/filter/nat move variants by scope. It never names a sibling explicitly, so differentiation is by resource path alone rather than by direct comparison.

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 when-to-use guidance: nothing says to pick this over update_raw_rule, nor that ordering determines firewall match precedence, nor any prerequisites. The 'Notes' block only restates parameter formats, so an agent must already know why reordering a raw rule is desirable.

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