Skip to main content
Glama

remove_wireless_access_list_entry

DestructiveIdempotent

Removes a wireless access list entry from a MikroTik RouterOS device by entry_id, helping update client allow or deny rules when access policies change.

Instructions

Legacy function - different in RouterOS v7.x

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": {
      "entry_id": "<entry_id>"
    },
    "name": "remove_wireless_access_list_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNo
entry_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.14.5
    • addedInput schema / properties / device
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Device"
      +}
  2. First observedv0.0.0

TDQS

D1.9/5.0
Behavior2/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, and the description does not contradict it. What the description could add but does not: what gets destroyed, what happens if the entry is absent (despite idempotency), and what 'different in v7.x' actually means for behavior or failure modes.

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 fragment is short but not concise in the useful sense: it front-loads an uninformative 'Legacy function' label and spends its only content on a vague version caveat rather than on what the tool does.

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, and annotations carry the destructive/idempotent profile. Even so, for a destructive two-parameter mutation with zero schema documentation, the definition is missing the target semantics, the v7 alternative, and any failure behavior.

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 both parameters, so the description is the only place to explain that entry_id is the required target identifier and device is an optional target selector. It mentions neither, leaving the agent to infer both from titles alone.

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 never states a verb or resource; 'Legacy function - different in RouterOS v7.x' identifies neither the object removed nor the removal action (only the tool name and annotation title do). It is a version caveat, not a purpose statement, so an agent must infer intent from the name alone.

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 a faint usage signal in the v7.x warning, implying caution or incompatibility on newer RouterOS, but no when-to-use rule, no preconditions, and no pointer to a preferred alternative when running v7. Nothing tells the agent when this tool is the right choice versus the v7 equivalent.

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