Skip to main content
Glama

remove_wireguard_peer

DestructiveIdempotent

Removes a WireGuard peer from a MikroTik device using its peer ID, helping revoke access and clean up the peer list.

Instructions

Removes a WireGuard peer from the MikroTik device.

Notes: peer_id: "*N" or "N" from list output e.g. "*2"

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": {
      "peer_id": "<peer_id>"
    },
    "name": "remove_wireguard_peer"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNo
peer_idYes

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

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=false, so the risk profile is documented. The description adds nothing beyond the identifier format: it does not say the peer's keys/config are permanently destroyed or whether dependent interfaces are affected. With annotations carrying the safety load, this is adequate but thin.

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?

One purpose sentence plus a short, front-loaded note on the identifier format. No filler; the note is separated clearly from the main statement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The output schema means return values need not be explained, and the destructive annotation covers risk. However, with one of two parameters undocumented and no guidance on the distinction between removing and disabling, the definition leaves real gaps for a destructive operation.

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% for two parameters, so the description must compensate. It does for peer_id by giving the accepted "*N" or "N" format and its origin in list output, which is genuinely useful, but the optional device parameter is entirely undocumented in both schema and description.

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?

"Removes a WireGuard peer from the MikroTik device" names a specific verb and resource, which is unambiguous. It does not distinguish removal from the sibling disable_wireguard_peer or remove_wireguard_interface, 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?

No guidance on when to remove rather than disable a peer, nor any note about prerequisites (e.g. that the peer ID must come from list_wireguard_peers). The agent must infer all selection logic from the 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