Skip to main content
Glama

create_vlan_interface

Creates a VLAN interface on a MikroTik device using a specified VLAN ID and parent interface, enabling network segmentation and tagged traffic management.

Instructions

Creates a VLAN interface on the MikroTik device with the given VLAN ID and parent interface.

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>",
      "vlan_id": "<vlan_id>",
      "interface": "<interface>"
    },
    "name": "create_vlan_interface"
  }
}

Input Schema

NameRequiredDescriptionDefault
arpNoenabled
mtuNo
nameYes
deviceNo
commentNo
vlan_idYes
disabledNo
interfaceYes
arp_timeoutNo
use_service_tagNo

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

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the description is not required to restate safety. Beyond those, it adds nothing: no statement of what happens on duplicate names, whether the change is committed immediately, or required device permissions, despite this being a mutating configuration tool.

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?

A single front-loaded sentence with no filler or repetition. It is efficient, though its brevity reflects under-specification rather than disciplined editing.

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?

An output schema exists, so return values need not be described. However, for a 10-parameter creation tool with zero schema descriptions, the one-sentence description does not come close to covering the arguments an agent must supply to create a working VLAN interface.

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 10 parameters, so the description must compensate, and it mentions only vlan_id and interface. Seven parameters (arp, arp_timeout, mtu, device, comment, disabled, use_service_tag) get no explanation of meaning, defaults, or constraints anywhere, and the 1-4094 VLAN ID range is left to the schema's minimum/maximum.

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 ('Creates a VLAN interface') and names the two identifying inputs (VLAN ID, parent interface), which is enough to distinguish it from create_wireguard_interface or create_wireless_interface by resource type. It stops short of any explicit sibling differentiation, so it lands at clear-but-not-differentiated.

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?

No guidance on when to use this versus update_vlan_interface, add_bridge_vlan, or the other create_* siblings, and no prerequisites such as the parent interface needing to exist or the name needing to be unique. The agent must infer all selection logic from the tool name alone.

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