Skip to main content
Glama

update_wireless_interface

Idempotent

Modify an existing wireless interface's name, SSID, device, comment, or enabled state to align MikroTik Wi-Fi settings with your network configuration.

Instructions

Updates an existing wireless interface's settings (name, SSID, enabled state, etc.).

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": "update_wireless_interface"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
ssidNo
deviceNo
commentNo
disabledNo
new_nameNo

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.8/5.0
Behavior2/5

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

Annotations already state readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds almost nothing beyond that: it does not say whether omitted fields are left unchanged or cleared, whether renaming via new_name breaks existing references, or whether changes require a device restart.

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

Conciseness4/5

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

One short sentence with the verb and scope front-loaded; nothing is wasted. The trailing "etc." is a minor weakness because it signals incompleteness rather than enumerating the remaining options.

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

Completeness3/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. However, for a 6-parameter mutation with zero schema descriptions and a name/new_name rename pattern, the definition leaves the agent guessing about null-handling and rename semantics.

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?

Schema description coverage is 0% across 6 parameters, so the description must carry the burden, yet it names only three concepts and omits device, comment, and new_name entirely. Most critically, it never clarifies the relationship between the required "name" (lookup key) and "new_name" (rename target), which is the highest-risk ambiguity in the schema.

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 pairs a specific verb ("Updates") with a specific resource ("an existing wireless interface's settings") and lists example fields, so the agent can tell it apart from create_/get_/remove_wireless_interface. It does not, however, distinguish itself from enable_wireless_interface or disable_wireless_interface, which also modify interface state.

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 explicit guidance on when to prefer this tool over the sibling enable_/disable_/set_wireless_passphrase tools, which overlap with the "enabled state" and SSID fields it mentions. The only implied guidance is the word "existing," which suggests the interface must already exist.

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