Delete a VPN user by providing their login. Used to revoke VPN access for a specific user.
Deletes the VPNUser
Error codes: inval, exist, noent, nomem, unsupp, inuse, busy, ioerror, size
| Name | Required | Description | Default |
|---|---|---|---|
| login | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
Input schema / properties / login / descriptionRemoved value: -"Login of the VPN user to delete"Output schema / (root)Previous value: -nullNew value: +{
+ "additionalProperties": true,
+ "type": "object"
+}v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
While error codes are listed, their meanings are not explained, and the description fails to disclose the destructive nature, irreversibility, or success/failure behavior. No annotations are provided, so the description carries the full burden, which it does not meet.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very brief but lacks structure. It omits important details like success output or parameter format. The error code list adds some information but is not well integrated.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simplicity of the tool (one parameter, delete operation) and the lack of annotations, the description is incomplete. It does not describe the return value, effect on the system, or how to interpret error codes, leaving significant gaps for an AI agent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description adds no information about the 'login' parameter beyond the schema. Schema coverage is 0%, and the description does not clarify what 'login' represents (e.g., username, email).
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states 'Deletes the VPNUser', indicating a specific verb and resource. It distinguishes from sibling delete tools for VPN client configs or connections, but lacks additional context about what constitutes a VPNUser.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives like delete_vpn_client_config_id or delete_vpn_connection_id. The description does not mention prerequisites or scenarios.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.