Skip to main content
Glama

enable_wireguard_peer

Idempotent

Activates a specified WireGuard peer on a MikroTik device by peer ID, allowing that peer to connect through the tunnel.

Instructions

Enables 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": "enable_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.4/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, idempotent, non-destructive, non-open-world operation, so the safety profile is covered. The description adds only the peer_id sourcing hint and says nothing about what happens when the peer is already enabled, whether the state change is immediate, or what errors arise for a bad ID. Credit for adding context, but limited.

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 short and front-loads the action, with the format detail following. The 'Notes:' block with stray indentation is slightly untidy and spends words on a formatting hint rather than behavior, but nothing is redundant.

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 tool is simple (2 params) and has an output schema, so return values need not be described. However, the undocumented 'device' parameter and the absence of any failure or already-enabled behavior leave the definition thinner than the mutation warrants.

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, and it only partially does: it explains the peer_id form ('*N' or 'N' taken from list output). The 'device' parameter is never mentioned in either the schema or the description, leaving a real gap. Partial compensation justifies a 3.

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 ('Enables a WireGuard peer'), which is clearly distinct from the sibling disable_wireguard_peer and remove_wireguard_peer. It does not explicitly name or contrast itself with any sibling, 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the note says peer_id comes 'from list output', which hints that list_wireguard_peers should be called first. There is no explicit when-to-use, when-not-to-use, or prerequisite/permission guidance.

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