Skip to main content
Glama

put_vpn_client_config_id

Update VPN server configuration including type, enabled state, port, IP ranges, and protocol-specific options for PPTP, OpenVPN, or IPsec.

Instructions

Update the VPNServerConfig

Error codes: inval, nomem, ioerror, nodev, noent, netdown, exist, busy, none, internal, authentication_failed, auth_failed, resolv_failed, connect_timeout, connect_failed, setup_control_failed, setup_call_failed, protocol, remote_terminated, remote_disconnect

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
id__pathYes(Path parameter)
idNoVPN server id
typeNoVPN server type — Values: `pptp`: PPTP VPN server; `openvpn`: OpenVPN server; `ipsec`: IPsec IKEv2 server
enabledNois the VPN server enabled
enable_ipv4Noenable IPv4 on this server
enable_ipv6Noenable IPv4 on this server
portNothe server port
min_portNoThis field indicate the minimum possible value for port (see ConnectionStatus ipv4_port_range)
max_portNoThis field indicate the maximum possible value for port (see ConnectionStatus ipv4_port_range)
port_ikeNoIPSec ike server port
port_natNoIPSec nat server port
conf_pptpNoonly available when type is PPTP
conf_openvpnNoonly available when type is OpenVPN
conf_ipsecNoonly available when type is IPsec
ip_startNostart of the IP range that will be used to give clients an IP
ip_endNoend of the IP range that will be used to give clients an IP
ip6_startNostart of the IPv6 range that will be used to give clients an IPv6
ip6_endNoend of the IPv6 range that will be used to give clients an IPv6

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

The description lists numerous error codes, providing some insight into possible failure modes. However, with no annotations, it lacks disclosure on destructive behavior, authorization needs, or side effects.

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

Conciseness3/5

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

The description is brief but includes a long list of error codes, which is helpful but not succinct. The main action is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite high schema coverage and an output schema, the description lacks explanation of return values, side effects, and tool behavior for a complex tool with 18 parameters. It feels incomplete.

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 coverage is 100%, so the description does not need to add parameter details. It adds no extra meaning beyond the schema, which is adequate but not enhanced.

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 clearly states 'Update the VPNServerConfig', indicating a specific verb and resource. However, it does not differentiate from sibling tools like put_vpn_openvpn_routed_config or post_vpn_client_config.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, context, or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Nelson-PROIA/freebox-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server