Skip to main content
Glama
AliKarami

MikroMCP

by AliKarami
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Manage VLAN Interface

manage_vlan
DestructiveIdempotent

Add, remove, enable, or disable RouterOS VLAN interfaces with idempotent name-based handling and dry-run previews to safely automate network changes.

Instructions

Add, remove, enable, or disable a VLAN interface. Idempotent by name: add returns already_exists when a VLAN with matching name, vlan-id, and parent interface exists. Supports dry-run mode.

Input Schema

NameRequiredDescriptionDefault
mtuNoMTU size (add only)
nameYesVLAN interface name — idempotency key, taken verbatim for remove/enable/disable; add accepts letters, digits, dot, hyphen, underscore, up to 64 chars
actionYesAction to perform
dryRunNoPreview changes without applying.
vlanIdNoVLAN ID (1-4094; required for add)
commentNoOptional comment (add only)
disabledNoWhether to create the VLAN disabled (add only)
routerIdNoRouter ID; omit to use the default router.
parentInterfaceNoParent interface name (e.g., ether1, bridge1; required for add)
confirmationTokenNoToken from a prior APPROVAL_REQUIRED response. Re-submit the identical call with this token to confirm the destructive action.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.16.0
    • changedInput schema / properties / name / description
      Previous value: -"VLAN interface name — idempotency key (alphanumeric, hyphens, underscores, max 15 chars)"New value: +"VLAN interface name — idempotency key, taken verbatim for remove/enable/disable; add accepts letters, digits, dot, hyphen, underscore, up to 64 chars"
    • removedInput schema / properties / name / maxLength
      Removed value: -15
    • addedInput schema / properties / name / minLength
      Added value: +1
    • removedInput schema / properties / name / pattern
      Removed value: -"^[a-zA-Z0-9_-]+$"
  2. Changed3 schema fields changedv1.6.0
    • changedInput schema / properties / dryRun / description
      Previous value: -"Preview changes without applying"New value: +"Preview changes without applying."
    • changedInput schema / properties / routerId / description
      Previous value: -"Target router identifier from the router registry"New value: +"Router ID; omit to use the default router."
    • changedInput schema / required
      Previous value: -[
-  "routerId",
-  "action",
-  "name"
-]New value: +[
+  "action",
+  "name"
+]
  3. Addedv1.5.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true; the description adds genuine value beyond them by defining the idempotency key precisely (name + vlan-id + parent interface) and the already_exists outcome, plus dry-run support. It omits the APPROVAL_REQUIRED/confirmationToken flow and that remove is irreversible, which the schema only hints at.

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?

Three tight sentences with the action set front-loaded, followed by the idempotency contract and dry-run flag. No repetition or filler.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 10-parameter destructive mutation with no output schema, the description covers the action set, idempotency semantics, and dry-run behavior. Return shape and the confirmation/approval flow are left to the schema, which is a minor gap given annotations already signal destructiveness.

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 100%, so the schema already explains every parameter thoroughly, including the confirmationToken flow. The description reinforces name as the idempotency key but adds no syntax or format detail beyond the schema; baseline 3 applies.

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 specific verbs (add, remove, enable, disable) against a specific resource (VLAN interface), so the agent can identify the operation without opening the schema. It does not explicitly contrast with siblings like manage_bridge or manage_interface_list, but the resource 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 Guidelines3/5

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

The four supported actions and the dry-run mention imply when the tool applies, but there is no explicit guidance on prerequisites, when to prefer it over alternatives, or what happens with partial matches. Usage is inferred rather than stated.

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