Skip to main content
Glama

create_ipv6_raw_rule

Creates IPv6 firewall raw rules that filter or redirect packets before connection tracking, enabling early blocking, jumping, logging, or address-list actions on RouterOS.

Instructions

Creates an /ipv6 firewall raw rule (applied before connection tracking).

Notes: chain: "prerouting" or "output", or a custom chain reached by jump. jump_target: required with action="jump". address_list (+ optional address_list_timeout, e.g. "1d"): required with add-src/dst-to-address-list. Prefix a matcher value with "!" to negate it. protocol: IPv6 uses "icmpv6", not "icmp". place_before: internal id ("*3") or print position ("0").

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": {
      "chain": "<chain>",
      "action": "<action>"
    },
    "name": "create_ipv6_raw_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
logNo
dscpNo
portNo
chainYes
limitNo
actionYes
deviceNo
commentNo
disabledNo
dst_portNo
protocolNo
src_portNo
hop_limitNo
tcp_flagsNo
log_prefixNo
dst_addressNo
jump_targetNo
packet_sizeNo
src_addressNo
address_listNo
icmp_optionsNo
in_interfaceNo
place_beforeNo
out_interfaceNo
dst_address_listNo
dst_address_typeNo
src_address_listNo
src_address_typeNo
in_interface_listNo
out_interface_listNo
address_list_timeoutNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.28.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this is a non-readonly, non-idempotent, non-destructive creation, and the description is consistent with that. The parenthetical 'applied before connection tracking' adds genuinely useful behavioral context that annotations cannot convey. However, it says nothing about creation side effects, ordering implications of the resulting rule, or failure modes, so it adds some value above the annotations but not rich detail.

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?

Front-loaded with a one-line purpose, then a compact notes block keyed by parameter, so an agent can scan to the relevant constraint. Minor flaw: the jump_target and address_list notes run together across line breaks, slightly obscuring which parameter each constraint belongs to.

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?

For a 31-parameter mutation tool with an output schema, the description covers purpose, ordering placement, and the non-obvious conditional dependencies plus the negation convention — the highest-risk areas. Remaining gaps (per-matcher semantics for addresses, ports, interfaces) are largely standard RouterOS fields and lower risk given the schema and output schema exist.

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% across 31 parameters, so the description is doing needed work: it explains the jump_target/action coupling, the address_list/action coupling, the place_before id-vs-position formats, and the broadly applicable '!' negation convention. That is meaningful semantics beyond a bare schema. Still, the large majority of matchers (src_address, ports, interfaces, hop_limit, etc.) get no treatment at all.

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 and resource ('Creates an /ipv6 firewall raw rule') and adds the qualifying clause 'applied before connection tracking', which distinguishes raw rules from the sibling filter-rule tools without needing to name them. It stops short of explicitly contrasting with create_raw_rule (IPv4) or create_ipv6_filter_rule, but the IPv6/raw specificity is enough to select correctly.

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 notes give real conditional guidance: jump_target is required with action=jump, address_list is required with add-src/dst-to-address-list, and place_before accepts an internal id or print position. What is missing is when to choose this over create_ipv6_filter_rule or create_raw_rule — no exclusions or alternatives are stated, so the usage guidance is conditional-parameter guidance rather than tool-selection guidance.

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