Skip to main content
Glama

remove_ipv6_raw_rule

DestructiveIdempotent

Removes an IPv6 firewall raw rule from a MikroTik RouterOS device by rule ID or print position, enabling cleanup of unwanted raw firewall entries.

Instructions

Removes an /ipv6 firewall raw rule.

Notes: rule_id: a RouterOS internal id ("*1A") or a 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": {
      "rule_id": "<rule_id>"
    },
    "name": "remove_ipv6_raw_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNo
rule_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.28.1

TDQS

B3.2/5.0
Behavior2/5

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

The annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered structurally. The description adds nothing behavioral beyond that — it does not say the deletion is permanent, whether dependent rules/state are affected, or what happens on an invalid id, and it ignores the device parameter entirely.

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?

Very short and front-loaded: the action is in the first sentence and the parameter note follows. The stray formatting of the 'Notes:' block is slightly untidy but no sentence is wasted.

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

Completeness5/5

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

For a two-parameter, single-target removal tool with a rich annotation set and an output schema, the definition covers the essential unknowns — chiefly the two accepted id formats. Remaining gaps (device semantics, irreversibility wording) are minor and partly implied by destructiveHint.

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. It does this well for rule_id by explaining that it accepts a RouterOS internal id like "*1A" or a print position like "0" — information absent from the schema. The other parameter, device, is left completely unexplained, so compensation is only partial.

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: 'Removes an /ipv6 firewall raw rule,' which distinguishes it from the filter/nat/address removal siblings and from the create/update/enable variants. It does not, however, explicitly distinguish it from the near-identical remove_raw_rule sibling.

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, no mention of alternatives (e.g., disable_ipv6_raw_rule as a reversible option), and no prerequisites or cautions. Usage is only inferable from the verb in the name.

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