Skip to main content
Glama

create_wireless_access_list

Creates a wireless access list entry on MikroTik RouterOS devices to control client access to wireless interfaces; behavior differs in RouterOS v7.x.

Instructions

Legacy function - different in RouterOS v7.x

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_wireless_access_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNo

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

C2/5.0
Behavior2/5

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

Annotations already declare this is a non-readOnly, non-idempotent mutation, so the safety profile is partly covered. The description adds only the vague claim that behavior differs across RouterOS versions, without saying what changes, what gets created, or what permissions are needed.

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?

It is short, but the brevity is under-specification rather than efficiency: a single fragment carries no actionable content and is not front-loaded with a purpose statement.

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 described, but for a mutating create tool with an undocumented parameter and a version caveat, the definition leaves the agent unable to determine what will be created or where.

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?

There is one optional 'device' parameter with 0% schema description coverage, and the description says nothing about it - not which device it refers to, nor what the default (null) means. With no schema documentation to lean on, the description fails to compensate.

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 says what the tool does; "Legacy function - different in RouterOS v7.x" only flags a version caveat. An agent must infer from the name alone that it creates a wireless access-list entry, and there is no differentiation from siblings such as create_wireless_security_profile or create_address_list_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?

The version note hints that this applies to older RouterOS, but there is no explicit when-to-use, no when-not-to-use, and no pointer to an alternative for v7.x. The agent is left to guess whether a newer tool should be used instead.

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