Skip to main content
Glama

move_ipv6_raw_rule

Idempotent

Reorder an IPv6 firewall raw rule by specifying its ID or current position and a 0-based destination index to change rule evaluation order on a MikroTik device.

Instructions

Moves an /ipv6 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_ipv6_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 readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds the useful fact that the operation reorders by position rather than editing content, but it says nothing about side effects on other rules' positions, permission requirements, or error behavior for out-of-range destinations.

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?

One sentence of purpose followed by two short notes; the essential operation is front-loaded and nothing is redundant. The notes block is a little spartan relative to the format used, but there is no wasted prose.

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 and rich annotations are present, so the description only needs to cover the operation and ambiguous inputs, which it largely does. The missing device parameter is the one notable hole for a mutation tool, but overall an agent can call this correctly from the definition.

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 parameter meaning, and it does explain that rule_id accepts either a RouterOS internal id ("*1A") or a print position ("0") and that destination is a 0-based index. However, the third parameter (device) is left entirely undocumented in both schema and description, which leaves a real 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?

"Moves an /ipv6 firewall raw rule to a different position" gives a specific verb and a fully qualified resource path, which distinguishes it from siblings like move_raw_rule, move_ipv6_filter_rule and move_nat_rule without naming them. The only thing missing is an explicit statement of the alternative, but the resource naming alone is unambiguous.

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 or when-not-to-use guidance, and no mention of prerequisites or the sibling tools that reorder other rule tables. The agent must infer from the name which table it applies to and when reordering is preferable to deleting and recreating a rule.

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