Skip to main content
Glama

disable_ipv6_raw_rule

Idempotent

Disables a specified IPv6 firewall raw rule on a MikroTik device to stop that rule from filtering or blocking matching traffic.

Instructions

Disables an /ipv6 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_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

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, idempotentHint=true and openWorldHint=false, so the safety profile is largely covered by structured data. The description adds nothing beyond that: it does not say what state the rule transitions to, whether it can be undone, or whether admin privileges are needed. With annotations doing the heavy lifting a 3 would be defensible, but a single restatement of the verb earns only 2.

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 short, front-loaded sentence with zero filler; the resource path is stated before anything else. It is perhaps over-compressed, but nothing in it is wasted or buried.

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?

An output schema exists, so return values need not be described. However, for a state-changing tool with an undocumented rule_id format and an ambiguous optional device parameter, the definition leaves the agent without enough information to call it correctly on the first attempt.

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' and 'device'. The description explains neither the expected identifier format for rule_id nor what omitting the nullable 'device' means (default router vs. specific one). This is the gap most likely to cause a failed call.

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 sentence names a specific verb (Disables) and a precise resource path (/ipv6 firewall raw rule), which distinguishes it from the enable/create/remove siblings and from the ipv6 filter-rule variants. It stops short of explicitly naming any alternative, so it is clear but not sibling-differentiated in prose.

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 prerequisite (e.g. that the rule must exist or that a device must be specified), and no mention of the counterpart enable_ipv6_raw_rule. The agent must infer everything about invocation context 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