Skip to main content
Glama

remove_address_list_entry

DestructiveIdempotent

Removes an IPv4 or IPv6 address list entry by list name and address, and clears any dynamic RouterOS entries derived from a removed hostname.

Instructions

Removes an address list entry by list name and address.

Notes: Removing a hostname entry also clears the dynamic entries RouterOS derived from it.

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": "remove_address_list_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNo
familyYes
addressYes
list_nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.22.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds real value with the note that removing a hostname entry also clears dynamic entries RouterOS derived from it, a side effect not visible in annotations. It does not say what happens when the entry is absent or whether the removal is immediate.

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 front-loaded sentence plus a short, genuinely informative note. No filler, though the note could be folded into the main sentence for tighter structure.

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 cover the destructive/idempotent profile. However, for a 4-parameter mutation tool with 0% schema coverage, the missing family and device semantics leave the definition short of complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 carry parameter meaning, yet it only mentions list_name and address. The family enum (ipv4/ipv6) and the optional device parameter are left entirely undocumented in both schema and description.

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 ("Removes an address list entry") and identifies the keying ("by list name and address"), which distinguishes it from create/update/get/disable siblings. It stops short of naming an alternative explicitly, so it is clear but not fully differentiated.

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

Usage Guidelines2/5

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

The description says how the entry is identified but never when to use this tool versus update_address_list_entry, disable_address_list_entry, or get_address_list_entry. No prerequisites or exclusions are given, leaving usage to inference from the verb alone.

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