Skip to main content
Glama
Sign In
wg-easy-mcp

wg-easy-mcp

by ni-c
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Generate one-time config link

generate_one_time_link

Generate a one-time download link for a client configuration to share with the intended user. Provide temporary access to the full WireGuard config without requiring authentication.

Instructions

Generate a one-time download link for a client configuration that can be shared with the end user. Requires WG_ENABLE_ONE_TIME_LINKS to be enabled on the wg-easy instance. SENSITIVE: anyone with the link can download the full client configuration without authentication — share it only with the intended user.

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": {
      "clientId": "<clientId>"
    },
    "name": "generate_one_time_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
clientIdYesNumeric ID of the client (see list_clients)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.2
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / clientId / maximum
      Added value: +9007199254740991
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

The description discloses the one-time nature, the server-side requirement (WG_ENABLE_ONE_TIME_LINKS), and a critical security behavior: the link grants unauthenticated access to the full config. This is valuable beyond the empty annotations, but it doesn't cover error handling or expiration details beyond 'one-time'.

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 concise sentences front-load the purpose and then add the requirement and security warning. No filler or redundancy.

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?

For a single-parameter tool with no output schema, the description adequately covers purpose, usage, and a critical security caveat. It lacks explicit error behavior when the environment flag is disabled, but this is minor given the simplicity.

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?

The input schema fully documents clientId with a clear description ('Numeric ID of the client (see list_clients)'). The description adds no additional parameter context, so the baseline score of 3 applies.

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?

Clearly states the tool generates a one-time download link for a client configuration, distinguishing it from sibling tools like get_client_config (which returns the config directly) and get_client_qrcode (which generates a QR code). The verb 'generate' and resource 'one-time download link' are specific.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Provides context that the link is meant to be shared with end users and requires WG_ENABLE_ONE_TIME_LINKS to be enabled. It implicitly suggests using this instead of direct config retrieval when sharing externally, though it doesn't explicitly name alternative tools.

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