Skip to main content
Glama
gxxHuang
by gxxHuang

delete_vpn_account

Remove a VPN account from an iKuai router by specifying the VPN type and user ID.

Instructions

删除 VPN 账号

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idYes
vpn_typeYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior1/5

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only says 'delete VPN account' and does not mention whether deletion is permanent, requires specific permissions, disconnects active sessions, or has other side effects. This is a significant gap for a destructive operation.

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

Conciseness4/5

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

The description is a single, front-loaded phrase '删除 VPN 账号' with no redundant words. It is concise and to the point, though it is also under-specified in other dimensions.

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

Completeness1/5

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

Given the tool has two required parameters, no annotations, and is a destructive operation, the one-line description is grossly insufficient. It lacks parameter explanations, usage context, and behavioral warnings, making it inadequate for safe and correct invocation.

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

Parameters1/5

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

The schema has no descriptions (0% coverage) for the two required parameters (user_id and vpn_type), and the description does not explain their meaning or acceptable values. The agent must guess that user_id identifies the account and vpn_type specifies the VPN protocol, with no guidance.

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 '删除 VPN 账号' clearly states the action (delete) and resource (VPN account), and distinguishes from sibling tools like delete_pppoe_account. However, it essentially restates the tool name without adding specific scope or differentiating details.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention, for example, that delete_pppoe_account should be used for PPPoE accounts, or any prerequisites or conditions for deleting VPN accounts.

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/gxxHuang/ikuai-mcp-server'

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