Skip to main content
Glama

remove_filter_rule

DestructiveIdempotent

Deletes a firewall filter rule from a MikroTik device by rule number or internal ID to clean up or update firewall policies.

Instructions

Removes a firewall filter rule from the MikroTik device.

Notes: rule_id: positional number from list output (e.g. "12") or internal ID (e.g. "*1A")

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_filter_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNo
rule_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.14.5
    • addedInput schema / properties / device
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Device"
      +}
  2. First observedv0.0.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false, and openWorldHint=false, so the safety profile is covered elsewhere. The description adds nothing behavioral beyond that — no statement that the removal is permanent, what happens if the rule_id does not exist, or which device is targeted when the parameter is omitted.

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 a short, clearly labeled Notes block; both front-load the essential information with no filler. The indented note formatting is slightly awkward but costs nothing in clarity.

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?

An output schema exists, so return values need not be described. For a destructive two-parameter removal tool, however, the definition omits targeting semantics (which device is used by default) and error behavior for an invalid or already-deleted rule_id.

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

Parameters4/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 the burden, and the Notes block explains the rule_id format (positional number from list output, e.g. "12", or internal ID, e.g. "*1A") — genuinely useful information absent from the schema. The `device` parameter and its null default are left unexplained, keeping it short of a 5.

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 a firewall filter rule from the MikroTik device.' The phrase 'firewall filter rule' implicitly separates it from IPv6, raw, and NAT variants in the sibling list, but no sibling is named explicitly, so an agent must infer the boundary.

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?

Gives no guidance on when to use this versus remove_raw_rule, remove_nat_rule, or remove_ipv6_filter_rule, and no prerequisites such as needed permissions or a confirmation step before a destructive delete.

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