Skip to main content
Glama

disable_address_list_entry

Idempotent

Disables an address list entry on a MikroTik device by specifying its address family, list name, and address, so you can stop traffic matching that entry without deleting it.

Instructions

Disables an address list entry.

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

D1.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, and the description is consistent with them but adds nothing beyond them. It does not mention that the entry is retained in disabled state rather than removed, nor any device/permission requirements.

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

Conciseness2/5

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

The single sentence is compact, but its brevity comes from under-specification rather than efficiency. Nothing is front-loaded beyond a restatement of the name.

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

Completeness2/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 needn't be described, but for a four-parameter mutation with zero schema coverage the definition leaves the identification of the target entry and device entirely unexplained. It is far below what is needed to call this correctly on a multi-device router fleet.

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

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across four parameters, so the description carries the full burden and provides none of it. It never explains the target device selector, the ipv4/ipv6 family enum, or how list_name and address together identify the entry.

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

Purpose2/5

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

The sentence 'Disables an address list entry' simply restates the tool name disable_address_list_entry with no added specificity. An agent can infer the mutation direction versus enable_address_list_entry and remove_address_list_entry, but only from the name, not from the description.

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?

There is no when-to-use guidance: nothing says when disabling is preferable to removing, how it differs from update_address_list_entry, or what prerequisites (device reachability, existing entry) must hold. Usage is left entirely to inference from the name.

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