Skip to main content
Glama

list_ipv6_raw_rules

Read-onlyIdempotent

Lists IPv6 firewall raw rules on a MikroTik device with filters for chain, action, protocol, addresses, interfaces, comments, and optional packet/byte counters.

Instructions

Lists /ipv6 firewall raw rules on the MikroTik device.

Notes: chain_filter, action_filter, protocol_filter: exact match. src/dst_address_filter, interface_filter (interfaces and interface lists), comment_filter: substring match. stats=True shows byte/packet counters.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_ipv6_raw_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
statsNo
deviceNo
chain_filterNo
dynamic_onlyNo
invalid_onlyNo
action_filterNo
disabled_onlyNo
comment_filterNo
protocol_filterNo
interface_filterNo
dst_address_filterNo
src_address_filterNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.28.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety is covered. The description adds genuinely non-obvious behavior: which filters match exactly versus by substring, that interface_filter also matches interface lists, and that stats=True surfaces byte/packet counters. It omits any note on result volume or pagination, keeping it from a 5.

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 compact notes block; the filter-semantics grouping is efficient and front-loaded. Sizing is appropriate for 12 parameters, though the notes line is dense and would scan better as a short bulleted list.

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

Completeness4/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 no explanation, and the filter/stats semantics are the main behavioral risk for this tool. The remaining gap is the `device` parameter's meaning and multi-device behavior, which matters given 12 optional parameters and no documented context.

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% across 12 parameters, so the description carries the burden. It does clarify the most ambiguous aspect — matching semantics for seven filter parameters — but leaves `device`, `dynamic_only`, `invalid_only` and `disabled_only` entirely unexplained; the booleans are largely self-evident, yet `device` (multi-device targeting) is not.

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 ("Lists /ipv6 firewall raw rules") plus the target system (MikroTik device), which cleanly separates it from the IPv4 `list_raw_rules` sibling. It stops short of explicitly naming that sibling or stating the IPv4-vs-IPv6 distinction as a routing rule, so it lands at 4 rather than 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The notes imply how to use the filters (exact vs substring, stats for counters), which is meaningful usage context. But there is no explicit when-to-use guidance, no mention of when to prefer `get_ipv6_raw_rule` for a single rule, and no stated alternatives for the IPv4 counterpart.

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