Skip to main content
Glama

vpn_server

Destructive

Manage incoming VPN servers on TP-Link routers: view or configure OpenVPN, PPTP, L2TP and WireGuard settings, enable or disable services, manage accounts, and inspect or disconnect clients.

Instructions

The router's VPN SERVERS (people dialling in). kind=openvpn|pptp|l2tp|wireguard; action=get | set (settings={...}) | enable | disable (CRITICAL) | accounts | accounts_add (account={...}) | accounts_update (key, account={...}) | accounts_remove (key) | connected | disconnect (key). Secrets masked unless reveal.

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": {
      "kind": "<kind>"
    },
    "name": "vpn_server"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNo
kindYes
applyNofalse (default) = dry run: show the plan, diff, warnings and risk, send nothing. true = send it.
actionNoget
revealNoShow secrets (passwords/keys) unmasked.
routerNoWhich router (see router_status 'routers'); default main.main
accountNo
settingsNo
confirm_tokenNoRequired with apply=true for CRITICAL changes: the token from the dry run (valid 5 minutes, bound to the exact plan and current router state).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is covered. The description adds two useful behavioral facts: that disable is '(CRITICAL)' and that secrets are 'masked unless reveal'. It does not describe what the destructive actions actually destroy (e.g. dropping connected sessions) or the dry-run/confirm_token requirement, which lives only in the schema.

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?

A single dense sentence that front-loads the resource and then enumerates action-to-parameter pairs with zero filler. The telegraphic style is appropriate for a multi-action tool and every clause carries information.

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 9-parameter, non-idempotent, destructive tool with no output schema, the description covers the action taxonomy and per-action argument mapping well. Gaps remain around return payloads (e.g. what 'connected' or 'accounts' yield) and the confirm-token workflow, but the core invocation guidance is present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 44% across 9 parameters, but the description compensates well by mapping each action to its required argument (set→settings, accounts_add→account, accounts_update→key+account, accounts_remove→key, disconnect→key) and explaining the reveal/masking behavior. The apply and confirm_token semantics are left to the schema, so it is not exhaustive.

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 names a specific resource and scope: 'The router's VPN SERVERS (people dialling in)', which immediately distinguishes inbound VPN server management from the sibling vpn_client (outbound/dial-out). An agent can identify the resource and its directionality without opening the schema.

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?

The inline action list ('get | set | enable | disable | accounts | ... | disconnect') effectively documents the available operations and the parenthetical '(people dialling in)' clarifies when this applies versus the client tool. It stops short of an explicit when-not-to-use rule or prerequisites, so it earns a 4 rather than a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.