Skip to main content
Glama

remove_raw_rule

DestructiveIdempotent

Removes a MikroTik RouterOS /ip firewall raw rule by specifying its internal ID or print position, helping clean up obsolete raw firewall entries.

Instructions

Removes an /ip 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_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
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=true, so irreversibility and safety are covered. The description adds the rule_id addressing format (internal id vs print position), which is useful behavioral context. It does not disclose the effect of the removal on firewall behavior or any permission/device requirements.

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?

Two short, front-loaded statements with no filler; the core purpose comes first and the ID format note follows. The embedded 'Notes:' block with stray indentation is slightly awkward but not wasteful.

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?

With a rich annotation set and an output schema, the description mostly suffices. The gaps are the undocumented 'device' parameter (default null, meaning unclear) and no statement of what removing a raw rule actually does to traffic.

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 coverage is 0%, so the description must carry the burden. It does well for rule_id, explaining both acceptable forms ('*1A' internal id or '0' print position) with examples, which the schema lacks entirely. The 'device' parameter is completely unaddressed, leaving half the parameters 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 and resource: 'Removes an /ip firewall raw rule.' The '/ip' qualifier distinguishes it from the ipv6 sibling (remove_ipv6_raw_rule) without needing to name it. It does not, however, differentiate from remove_filter_rule or explain the raw-vs-filter distinction.

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 guidance on when to remove a rule versus when to use disable_raw_rule, which is an obvious alternative in the sibling set. No prerequisites or side-effect context (e.g., that traffic previously matched will no longer be blocked/marked). Usage is only implied by the verb.

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