Skip to main content
Glama

get_ipv6_raw_rule

Read-onlyIdempotent

Retrieves detailed information about a specific IPv6 firewall raw rule using a RouterOS internal ID or print position.

Instructions

Gets detailed information about a specific /ipv6 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_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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that about behavior — no error/not-found semantics, no note on whether the returned detail includes counters or dynamic flags. Adequate but thin given annotations carry most of the load.

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 short, front-loaded sentences: the purpose first, then a targeted note on the one parameter that needs explanation. No filler or redundancy.

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

Completeness3/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, and the required parameter is well covered. However, the 'device' parameter is undocumented in both schema and description, leaving a gap for a tool that presumably operates across multiple RouterOS devices.

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%, so the description must compensate, and it does for the critical required parameter by explaining that rule_id accepts either a RouterOS internal id ("*1A") or a print position ("0") — information absent from the schema. The optional 'device' parameter is left entirely undocumented, which keeps it from a 5.

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 detailed information') and resource ('a specific /ipv6 firewall raw rule'), which clearly separates it from list_ipv6_raw_rules and the mutation siblings. It does not explicitly name a sibling alternative, but the singular 'specific' framing makes the distinction inferable.

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?

Usage is only implied: the agent can infer this is for fetching one rule by id rather than listing. There is no explicit when-to-use/when-not guidance, no mention of what happens if the rule does not exist, and no pointer to list_ipv6_raw_rules for discovery of ids.

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