Skip to main content
Glama

set_wireless_security_profile

Assign a security profile to a wireless interface on legacy MikroTik RouterOS; note this function is not supported in RouterOS v7.x.

Instructions

Legacy function - not supported 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": {
      "interface_name": "<interface_name>",
      "security_profile": "<security_profile>"
    },
    "name": "set_wireless_security_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNo
interface_nameYes
security_profileYes

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

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

Annotations declare a non-readOnly, non-idempotent, non-destructive mutation, but say nothing about version compatibility; the description adds the meaningful fact that the operation is unsupported on RouterOS v7.x, implying likely failure there. It still omits what the call changes on the device, whether it errors or silently no-ops on v7, and whether existing profiles are overwritten. Given the annotation coverage, a 3 reflects real added context with clear remaining gaps.

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

Conciseness3/5

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

It is a single short sentence with zero padding, which is structurally clean. But it spends its only sentence on a deprecation caveat rather than front-loading purpose, so the brevity reflects under-specification rather than discipline.

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?

For a mutation tool with two required parameters at 0% schema coverage, the description provides almost nothing an agent needs to call it correctly except the version warning. An output schema exists, so return values need not be explained, but the input contract and the effect of the call are undocumented in both the schema and the description.

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 three parameters (device, interface_name, security_profile) and the description supplies no meaning for any of them. Nothing explains what a 'security profile' string refers to, whether it must already exist, or what the device parameter selects. The description does nothing to compensate for the total schema coverage gap.

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 what the tool does; the only content is a compatibility notice ("Legacy function - not supported in RouterOS v7.x"). Any sense of a verb+resource comes solely from the tool name, not the text. It does at least signal this is a legacy/write-style configuration call, so it is not actively misleading, but purpose is essentially absent.

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?

It gives a negative condition (do not use on RouterOS v7.x), which is genuine when-not guidance and better than nothing. However, it names no alternative among the many siblings (e.g., create_wireless_security_profile) and gives no positive condition under which this tool should be used, leaving the agent to guess whether a v6 path is intended.

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