Skip to main content
Glama

list_raw_rules

Read-onlyIdempotent

Lists /ip firewall raw rules on a MikroTik device and filters by chain, action, protocol, addresses, interfaces, or comments; enable stats to show counters.

Instructions

Lists /ip 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_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

A4/5.0
Behavior3/5

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

Annotations already cover readOnly, idempotent, and non-open-world behavior, so the safety story is handled. The description does add real behavioral detail in the matching semantics (exact vs substring, interface lists included) and what stats=True returns. It stops short of saying what happens on an unreachable/unknown device, whether results are paginated, or how the device parameter selects a target.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One identification sentence followed by a compact grouped note; nothing is repeated from the schema and the matching-mode distinction is front-loaded where an agent will see it.

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?

Read-only list tool with an output schema, so return values need no explanation. Given 12 optional parameters, the filter semantics note covers the highest-risk ambiguity; the residual gap is the device parameter and the three '_only' filters, which are low-risk but not addressed.

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% across 12 parameters, so the description has to carry the load. It successfully disambiguates the non-obvious part by grouping chain_filter/action_filter/protocol_filter as exact match and src/dst_address_filter/interface_filter/comment_filter as substring match, plus what stats toggles. The device, dynamic_only, invalid_only, and disabled_only parameters are left to their self-explanatory names.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Uses a specific verb plus resource ('Lists /ip firewall raw rules on the MikroTik device'), and the slash-path scoping tells an agent this is neither the IPv6 raw set nor the filter/nat rule sets without needing to open a sibling schema.

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?

There is no explicit when-to-use or when-not-to-use statement and no named alternative (e.g. list_ipv6_raw_rules or list_filter_rules), so the agent must infer the context from the '/ip firewall raw' path. That implied scoping is understandable but not spelled out.

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