Skip to main content
Glama

update_ipv6_raw_rule

Idempotent

Updates an existing MikroTik IPv6 firewall raw rule by ID or position, letting you change match conditions, action, logging, or clear optional fields.

Instructions

Updates an existing /ipv6 firewall raw rule.

Notes: rule_id: a RouterOS internal id ("*1A") or a print position ("0"). Pass "" to clear an optional matcher (e.g. src_address="").

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>"
    },
    "name": "update_ipv6_raw_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
logNo
dscpNo
portNo
chainNo
limitNo
actionNo
deviceNo
commentNo
rule_idYes
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
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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly=false, idempotent=true, and destructive=false, so the safety profile is covered. The description adds useful context on rule_id formats and clearing optional matchers with an empty string, but it does not explain partial-update semantics, validation behavior, or what happens to omitted parameters.

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 short and front-loaded: it states the action first, then provides two compact notes. There is no unnecessary wording or buried guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is a 31-parameter mutation with no schema parameter descriptions, and the description does not explain how omitted parameters behave or give per-parameter meaning beyond rule_id and clearing. Output schema and annotations cover return values and safety, but the description remains too sparse for this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 31 parameters and 0% schema description coverage, the description documents only rule_id and a generic way to clear optional matchers. The remaining parameters are left to bare titles, which is a significant compensation gap for a complex update tool.

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 states a specific verb and resource: "Updates an existing /ipv6 firewall raw rule." The IPv6 raw scope distinguishes it from IPv4 raw and IPv6 filter siblings by resource, though it does not explicitly name alternatives.

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?

"Updates an existing" implies this is for modifying rules rather than creating them, and the notes explain rule_id formats and how to clear optional matchers. However, it gives no explicit when-not guidance or named alternatives such as create_ipv6_raw_rule or update_ipv6_filter_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