Skip to main content
Glama

add_wireguard_peer

Add a WireGuard peer to a MikroTik interface using its public key and allowed IP addresses, with optional endpoint and persistent keepalive settings.

Instructions

Adds a WireGuard peer (with public key and allowed addresses) to an interface on the MikroTik device.

Notes: allowed_address: CIDR, comma-separated for multiple e.g. "10.0.0.2/32" or "10.0.0.0/24,192.168.0.0/24" endpoint_address: remote host IP or hostname e.g. "203.0.113.1" persistent_keepalive: seconds as string e.g. "25"

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": {
      "interface": "<interface>",
      "public_key": "<public_key>",
      "allowed_address": "<allowed_address>"
    },
    "name": "add_wireguard_peer"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNo
commentNo
disabledNo
interfaceYes
public_keyYes
endpoint_portNo
preshared_keyNo
allowed_addressYes
endpoint_addressNo
persistent_keepaliveNo

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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the safety profile is covered. The description adds that the peer is attached to an existing interface on the device, but it omits important behavior for a non-idempotent mutation: what happens on a duplicate public_key, whether the change is applied immediately or requires a commit, and what permissions are needed.

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 core action is front-loaded in one sentence and the three follow-up notes are compact and scannable. The notes block is slightly under-formatted but contains no 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?

The criteria weights are 25/20/20/15/10/10, and this dimension is the 10% one; with annotations present and an output schema available, the description needn't explain return values, so the remaining gap is mainly prerequisites and duplicate-handling behavior. For a 10-parameter non-idempotent mutation tool its coverage is adequate but not thorough.

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 0% across 10 parameters, so the description carries the full burden; the notes give genuinely non-inferable format detail for allowed_address (comma-separated CIDR), endpoint_address (IP or hostname) and persistent_keepalive (seconds as a string). However, seven parameters — including required interface and public_key, plus preshared_key, endpoint_port, device, disabled and comment — get no guidance at all.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence names a specific verb (adds) and resource (WireGuard peer) plus the parent resource (interface on the MikroTik device), and the wording inherently separates it from the sibling update_wireguard_peer, remove_wireguard_peer, and list_wireguard_peers.

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 explicit when-to-use guidance: nothing says to use this instead of update_wireguard_peer, nothing states that the target interface must already exist (see create_wireguard_interface), and no prerequisites or failure conditions are given.

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