Skip to main content
Glama

disable_wireguard_peer

Idempotent

Disable a WireGuard peer by peer ID to stop its VPN access or deactivate its tunnel connection. Use it to revoke peer connectivity on MikroTik RouterOS.

Instructions

Disables a WireGuard peer.

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": "disable_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

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true, so the safety profile is covered elsewhere. The description adds nothing beyond the verb itself: it doesn't say whether disabling an already-disabled peer errors, whether traffic is immediately dropped, or whether the config persists across reboot, which are the questions an agent actually has for a mutation tool.

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 sentence is front-loaded and waste-free. The 'Notes:' block is slightly awkwardly formatted but short and directly useful for constructing peer_id, so nothing meaningful should be cut.

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?

An output schema and rich annotations exist, so return values and safety are covered elsewhere. The remaining gaps are the undocumented device parameter and the absence of any pointer to list_wireguard_peers for obtaining peer ids, which for a two-parameter mutation tool is a real but not fatal omission.

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%, so the description must carry the burden. It does a good job on peer_id by explaining the '*N' / 'N' formats taken from list output, but the second parameter, device, is never mentioned, leaving an agent to infer which device the peer lives on.

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 states a specific verb and resource: 'Disables a WireGuard peer.' An agent can tell exactly what operation occurs. It does not explicitly contrast with sibling tools such as enable_wireguard_peer or remove_wireguard_peer, so differentiation is left to the name alone.

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 guidance on when to disable versus enabling, updating, or removing a peer, and no prerequisites or side effects are mentioned. The only usage-adjacent hint is that peer_id comes 'from list output,' which implies list_wireguard_peers as a source but never names it.

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