Skip to main content
Glama

remove_wireless_security_profile

DestructiveIdempotent

Removes a legacy wireless security profile from a MikroTik device; use only where supported, as RouterOS v7.x does not support this function.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
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.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered structurally. The description adds one genuinely new behavioral fact the annotations cannot express: the tool is non-functional on RouterOS v7.x. It does not say what is destroyed, whether removal cascades to attached interfaces, or what error surfaces on v7.

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?

One short front-loaded sentence with no filler, which is structurally sound. However the brevity reflects under-specification rather than efficiency: the single sentence omits purpose, parameters, and alternatives entirely.

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 destructive mutation with 0% parameter coverage, the definition is inadequate beyond the version warning. An output schema exists, so return values need not be explained, but the description should still cover what the profile removal affects and what happens when invoked on an unsupported version.

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% for both parameters ('name' required, 'device' optional), so the description carries the full burden and provides nothing. No indication of naming format, whether 'name' must match an existing profile, or what 'device' scopes.

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 information is a deprecation notice ('Legacy function - not supported in RouterOS v7.x'). An agent must infer the removal behavior from the tool name alone, though the version caveat at least signals the tool is unusable in current environments.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It implies when NOT to use the tool (RouterOS v7.x) but never states the supported condition explicitly (e.g. v6.x) nor points to an alternative such as set_wireless_security_profile or any v7 replacement. This is a partial usage constraint rather than real routing guidance.

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