Skip to main content
Glama
ni-c

wg-easy-mcp

by ni-c
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Update WireGuard client

update_client

Update a WireGuard client's specific settings—name, enabled, DNS, MTU, addresses, expiry, or allowed IPs—while preserving all other configuration.

Instructions

Update a WireGuard client. Only the provided fields are changed; all other settings are preserved.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dnsNoDNS servers for the client, or null to use the server default
mtuNoMTU for the client
nameNoNew display name
enabledNoEnable or disable the client
clientIdYesNumeric ID of the client (see list_clients)
expiresAtNoExpiry date as ISO string, or null to remove the expiry
allowedIpsNoCIDRs routed through the tunnel on the client side, or null to use the server default
ipv4AddressNoIPv4 address of the client
ipv6AddressNoIPv6 address of the client
serverAllowedIpsNoAdditional CIDRs the server routes to this client
persistentKeepaliveNoPersistent keepalive interval in seconds (0 = off)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / expiresAt / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / expiresAt / type
      Added value: +[
+  "string",
+  "null"
+]
  2. Changed8 schema fields changedv0.2.2
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / clientId / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / expiresAt / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / expiresAt / type
      Removed value: -[
-  "string",
-  "null"
-]
    • addedInput schema / properties / mtu / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / mtu / minimum
      Added value: +-9007199254740991
    • addedInput schema / properties / persistentKeepalive / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / persistentKeepalive / minimum
      Added value: +-9007199254740991
  3. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations are empty, so the description carries the burden of behavioral disclosure. It explicitly states that only provided fields are changed and all other settings are preserved, which is important partial-update semantics. It does not mention permissions or error behavior, so it is not a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with no filler. The most important behavioral detail, partial updates with preservation of other settings, is included immediately after the purpose 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 description covers the core update semantics, but with no annotations and no output schema, there is no mention of return values, error behavior, or how this relates to dedicated enable/disable tools. For an 11-parameter mutation tool, slightly more context would be helpful.

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 100%, so the schema already documents all parameters. The description adds only the general partial-update concept and no per-parameter detail, which matches the baseline for full schema coverage.

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 description states a clear verb and resource: 'Update a WireGuard client.' The added sentence about partial updates distinguishes it from create/delete/get tools and clarifies its scope. This is unambiguous and easily distinguished from sibling tools like create_client or delete_client.

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?

The description implies usage: use when you need to modify an existing client. However, it does not explicitly state when to prefer this over siblings like enable_client or disable_client, nor does it mention exclusions or alternatives.

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