Skip to main content
Glama

enable_address_list_entry

Idempotent

Enable an existing MikroTik address list entry by specifying its IP family, list name, and address, with an optional target device.

Instructions

Enables 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": "enable_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, destructiveHint=false, idempotentHint=true, and openWorldHint=false, so the safety profile is covered structurally. The description adds nothing beyond that — no explanation of what state change occurs, what happens if the entry is already enabled, or whether it requires the entry to pre-exist.

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 short, but it is under-specified rather than concise — it occupies a full description slot with a tautology that could have carried real information.

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 need not be explained, which provides some relief. However, this is a state-changing operation on a network device with four undocumented parameters and no behavioral context, which is inadequate for the tool's complexity.

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 (device, family, address, list_name), and the description does not mention any of them. With the schema carrying no semantics, the description bears full responsibility for clarifying address format, list scoping, or the meaning of the optional device parameter, and it fails to do so.

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 description reads 'Enables an address list entry,' which is a near-verbatim restatement of the tool name with no added specificity. It does not distinguish this from siblings such as disable_address_list_entry or update_address_list_entry, nor does it explain what 'enabling' means for an entry.

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, no prerequisites, and no mention of alternatives like disable_address_list_entry. The agent must infer the usage context entirely from the name and sibling list.

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