Skip to main content
Glama

create_wireless_interface

Create a wireless interface on a MikroTik device with automatic RouterOS v6/v7 syntax detection, using options for SSID, band, mode, and security profile.

Instructions

Creates a wireless interface on the MikroTik device (auto-detects RouterOS v6/v7 syntax).

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

Input Schema

NameRequiredDescriptionDefault
bandNo
modeNo
nameYes
ssidNo
deviceNo
commentNo
disabledNo
frequencyNo
radio_nameNo
channel_widthNo
security_profileNo

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.9/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the write-and-non-idempotent profile is covered. The description adds one genuinely useful behavioral fact — automatic RouterOS v6/v7 syntax detection — but says nothing about required permissions, what happens on name collision, or whether the interface is created enabled by default.

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

Conciseness5/5

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

A single sentence, front-loaded with the action and resource, with the parenthetical adding real information rather than filler. Nothing is wasted or buried.

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 an 11-parameter creation tool the definition is far too thin: no parameter meaning, no prerequisites, no note that only 'name' is required, and no hint about which optional fields are commonly needed. It leaves the agent to reverse-engineer most of the call from schema titles.

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?

With 11 parameters and 0% schema description coverage, the description carries the full burden of explaining parameters and adds none of it: band, mode, channel_width, security_profile, radio_name, device, frequency and the rest are unmentioned. Enum values exist in the schema but their meaning (e.g. ap-bridge vs station-bridge, which band applies to which radio) is left entirely unexplained.

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?

The description gives a specific verb and resource ('Creates a wireless interface on the MikroTik device'), which is clearly distinguishable from sibling creators like create_vlan_interface and create_wireguard_interface. It stops short of naming those siblings or clarifying scope relative to update_wireless_interface, but the core purpose is unambiguous.

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 guidance on when to use this versus update_wireless_interface, no mention of prerequisites such as the wireless package or an existing security_profile, and no note on failure conditions like a duplicate name. The agent must infer all of this from sibling names and the schema.

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