Skip to main content
Glama

update_vlan_interface

Idempotent

Modify an existing VLAN interface's settings on a MikroTik device to change parameters such as VLAN ID, MTU, ARP, interface binding, or administrative state.

Instructions

Updates an existing VLAN interface's settings on the MikroTik device.

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": "update_vlan_interface"
  }
}

Input Schema

NameRequiredDescriptionDefault
arpNo
mtuNo
nameYes
deviceNo
commentNo
vlan_idNo
disabledNo
new_nameNo
interfaceNo
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?

The annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=true, so the safety profile is covered. The description adds nothing beyond restating that it updates settings: it does not say whether omitted parameters are preserved (partial vs full update), that renaming via new_name changes the interface's identity, or that changing vlan_id may disrupt traffic.

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?

A single front-loaded sentence with no wasted words, which is good structurally. But at this length for an 11-parameter mutation tool, the 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 an 11-parameter update with 0% schema coverage and no annotations-level detail on partial update semantics, the description leaves far too much for the agent to infer before calling it correctly.

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 11 parameters, and the description explains none of them. Critical ambiguity is left unresolved – name identifies the target while new_name renames it, and fields like vlan_id, interface, use_service_tag and arp carry meaning the bare schema titles do not convey.

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: "Updates an existing VLAN interface's settings on the MikroTik device." An agent can tell it is the modify operation versus create/remove/get siblings from the name and sentence, though the description never explicitly contrasts them.

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?

Usage is only implied by the word "existing" – it presumes a VLAN interface already exists and is identified by name. There is no explicit when-to-use versus update_bridge_vlan or update_wireguard_interface, no prerequisites, and no note about what happens to fields left unset.

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