Skip to main content
Glama

update_wireguard_interface

Idempotent

Update settings for an existing WireGuard interface on a MikroTik device, including MTU, listen port, private key, name, comment, and enabled/disabled state.

Instructions

Updates an existing WireGuard 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_wireguard_interface"
  }
}

Input Schema

NameRequiredDescriptionDefault
mtuNo
nameYes
deviceNo
commentNo
disabledNo
new_nameNo
listen_portNo
private_keyNo

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

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

Annotations already declare this a non-read-only, idempotent, non-destructive, closed-world mutation, so the safety profile is covered. The description adds nothing about how unspecified fields are treated (left unchanged vs nulled), that 'private_key' rotation invalidates existing peers, or that renames via 'new_name' may break peer references.

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 sentence with no padding, but its brevity comes from omission rather than efficiency. There is no structure to prioritize which fields matter most.

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 explained, but for an 8-parameter idempotent mutation with zero schema documentation the description is far too thin. Key behaviors such as partial updates and key rotation are unaddressed.

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 8 parameters, so the description carries the full burden and fails it. It never mentions mtu, listen_port, private_key, comment, device, disabled, or the rename-via-new_name behavior, leaving every parameter's meaning and format undocumented.

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 WireGuard interface's settings') and narrows scope to the MikroTik device. It does not distinguish itself from nearby siblings such as update_wireguard_peer or the enable/disable_wireguard_interface pair, so it stops short of a 5.

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?

There is no when-to-use or when-not-to-use guidance. An agent gets no hint that toggling 'disabled' might be better served by enable_wireguard_interface/disable_wireguard_interface, or that creation belongs to create_wireguard_interface; only the word 'existing' implies a precondition.

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