Skip to main content
Glama

disable_raw_rule

Idempotent

Disable a MikroTik /ip firewall raw rule by rule ID to stop it from matching and acting on traffic.

Instructions

Disables an /ip firewall raw rule.

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": "disable_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

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=true, and the description adds nothing beyond that: it doesn't say the rule persists but stops matching traffic, whether it can be re-enabled, or what happens if already disabled. With no annotations the burden would be higher, but even at the lowered bar it contributes essentially nothing.

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?

A single front-loaded sentence with zero filler; it is efficient, though the terseness reflects missing content rather than disciplined compression.

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?

For a state-changing network device operation with an undocumented parameter schema, the definition should explain the device targeting, the effect of disabling (traffic no longer matched rather than configuration deleted), and idempotency behavior; only the bare action is given. The presence of an output schema removes the need to describe return values, which is the one thing in its favor.

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?

Schema description coverage is 0% for two parameters (rule_id, device), so the description must compensate and does not — neither the identifier format nor the device selector (targeting a specific router among several) is explained.

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 (disables) and resource (/ip firewall raw rule), and the '/ip' namespace distinguishes it from the ipv6 sibling tools without needing to open a schema. It does not, however, explicitly contrast itself with enable_raw_rule or remove_raw_rule.

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?

No guidance on when to disable versus remove or update a rule, and no prerequisites (such as the rule needing to exist or be currently enabled). The agent must infer usage from the name alone.

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