Skip to main content
Glama

create_wireguard_interface

Creates a WireGuard interface on a MikroTik device, enabling VPN tunnels with configurable name, MTU, listen port, private key, and disabled state.

Instructions

Creates a WireGuard interface 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": "create_wireguard_interface"
  }
}

Input Schema

NameRequiredDescriptionDefault
mtuNo
nameYes
deviceNo
commentNo
disabledNo
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.6/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, idempotentHint=false, and openWorldHint=false, so the safety profile is largely covered. The description only restates that creation happens and adds "on the MikroTik device" as context; it does not disclose side effects, uniqueness constraints, required private key behavior, or what happens on name conflicts.

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?

The definition is a single front-loaded sentence with no filler. It is concise and structurally clear, though its brevity contributes to the missing usage and parameter context.

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 creation tool with 7 parameters, one required field, and no schema descriptions, this description is too thin. Output schema exists, so return-value explanation is not required, but the definition should still cover key prerequisites, parameter expectations, and creation-specific behavior.

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?

The schema has 7 parameters with 0% description coverage, and the description does not explain any of them. It omits even the required name parameter and the private_key, listen_port, mtu, device, comment, and disabled options, so it adds no semantic meaning beyond the bare schema titles.

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?

The description gives a specific verb and resource: "Creates a WireGuard interface on the MikroTik device." This is clear enough to distinguish it from peer tools like create_vlan_interface or add_wireguard_peer, but it does not explicitly differentiate it from the sibling update_wireguard_interface or explain scope beyond the object type.

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?

The description provides no when-to-use guidance, no prerequisites, and no alternatives. It does not say when this should be used instead of update_wireguard_interface, nor does it mention required preconditions such as a unique interface name or key material.

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