Skip to main content
Glama

get_raw_rule

Read-onlyIdempotent

Retrieve detailed information about a specific /ip firewall raw rule by RouterOS internal ID or print position to inspect its configuration.

Instructions

Gets detailed information about a specific /ip firewall raw rule.

Notes: rule_id: a RouterOS internal id ("*1A") or a print position ("0").

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

A3.6/5.0
Behavior3/5

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

Annotations already establish that this is a read-only, idempotent, non-open-world operation. The description adds the accepted rule_id formats, but does not describe error behavior, permissions, or other behavioral context beyond the annotations, so the added value is modest.

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?

Two compact sentences plus a short note, front-loaded with the purpose. Every part contributes directly to identifying the tool or interpreting rule_id.

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?

For a simple two-parameter getter with annotations and an output schema, this gives enough information to call the tool correctly. The undefined device parameter and lack of explicit sibling routing are the main remaining gaps.

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%, so the description must explain both parameters. It gives a useful dual format for rule_id ('*1A' or '0'), but leaves the optional device parameter completely undefined.

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 ('Gets') and resource ('specific /ip firewall raw rule'), making clear this is a single-rule lookup. It does not explicitly distinguish itself from sibling getters such as get_ipv6_raw_rule, get_filter_rule, or list_raw_rules, so it is not a 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 required rule_id and the word 'specific' imply this is for retrieving one known rule, while list_raw_rules would be for enumeration. However, the description never states that alternative or any when-not conditions, so guidance is inferable but not explicit.

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