Skip to main content
Glama

set_wireless_passphrase

Idempotent

Sets or changes the WiFi passphrase on a RouterOS v7 wireless interface and can update authentication types in the same operation.

Instructions

Sets the WiFi passphrase directly on a RouterOS v7 wireless interface (/interface wifi or wifiwave2).

Notes: authentication_types: comma-separated RouterOS auth types, e.g. "wpa2-psk,wpa3-psk"; unset keeps the current setting.

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>",
      "passphrase": "<passphrase>"
    },
    "name": "set_wireless_passphrase"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
deviceNo
passphraseYes
authentication_typesNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.19.4

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds real value by clarifying that the passphrase is written directly to the interface rather than to a security profile, and that omitting authentication_types preserves the existing value. It does not disclose side effects such as existing clients being disconnected or required permissions.

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?

The core action is front-loaded in the first sentence and the notes section is short and relevant. No filler, though the notes block is a single item and could have been folded into the main sentence.

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 described, and annotations cover the mutation profile. However, for a 4-parameter mutation tool with zero schema descriptions, the definition leaves the 'device' parameter and the effect on connected clients undocumented.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the load. It does well on the least obvious parameter, giving a concrete example format for authentication_types and its unset semantics, but leaves 'device' and the distinction between 'name' and 'device' 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?

States a specific verb and resource ('Sets the WiFi passphrase') and scopes it to RouterOS v7 wireless interfaces, naming the config paths (/interface wifi or wifiwave2). It does not differentiate itself from the sibling set_wireless_security_profile, which is the most likely confusion point for an agent.

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 when-to-use or when-not-to-use guidance, and no mention of prerequisites such as the interface existing or the security profile needing to support PSK. The only conditional behavior given is that an unset authentication_types keeps the current setting.

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