Skip to main content
Glama

create_address_list_entry

Add an IPv4 or IPv6 address or hostname entry to a MikroTik firewall address list, with optional comment, timeout, or disabled state.

Instructions

Adds an entry to an IPv4 or IPv6 firewall address list.

Notes: address: an address or prefix; a hostname is also accepted and RouterOS adds a dynamic child entry per resolved address. timeout: RouterOS duration e.g. "1h". An entry with a timeout is dynamic, so it does not survive a reboot. list_name is matched exactly, including any leading or trailing spaces.

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": {
      "family": "<family>",
      "list_name": "<list_name>",
      "address": "<address>"
    },
    "name": "create_address_list_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNo
familyYes
addressYes
commentNo
timeoutNo
disabledNo
list_nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.22.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the description's job is to add context, and it does: hostnames generate dynamic child entries per resolved address, timeout-based entries are dynamic and do not survive a reboot, and exact string matching applies to list_name. It stops short of 5 because it does not say whether a missing list is auto-created, how duplicates are treated, or what errors to expect.

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?

Front-loaded with a one-line statement of purpose followed by three tight, itemized notes; every sentence carries information. Formatting is slightly ragged with the indented note bodies, but no content is wasted.

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 explained, and annotations carry the safety profile. However, for a 7-parameter mutation tool with zero schema descriptions, the undefined device, comment and disabled parameters plus the unresolved question of pre-existing lists leave real gaps an agent would need to guess about.

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 7 parameters, so the description must carry the load and it only partly does: it explains address, timeout and list_name, and family is implied by 'IPv4 or IPv6', but device, comment and disabled receive no explanation anywhere. Coverage of roughly half the parameters with genuinely non-obvious semantics for the ones it does cover warrants a middle score.

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 description opens with a specific verb and resource: 'Adds an entry to an IPv4 or IPv6 firewall address list.' That is unmistakably distinct from the sibling operations (remove, enable, update, get), even though no sibling is named explicitly, so it falls just short of the top tier reserved for explicit sibling differentiation.

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 statement of when to use this versus update_address_list_entry or remove_address_list_entry, nor any prerequisite about whether the list must already exist. The 'list_name is matched exactly, including any leading or trailing spaces' note functions as a useful usage caveat but is framed as a parameter note rather than when-to-use guidance.

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