Skip to main content
Glama
Sign In
vpnhop

vpnhop

by kylepantall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Disconnect a VPN profile

disconnect
Idempotent

Stops and removes the VPN tunnel container for a specified profile, cleaning up resources when that connection is no longer needed.

Instructions

Stops and removes the tunnel container for a profile.

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": {
      "profile": "<profile>"
    },
    "name": "disconnect"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileYesProfile name from list_profiles.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

The description adds real behavioral detail beyond the annotations: the operation both stops and removes the container, not merely closes a connection. It does not say whether the stored profile configuration survives, or what happens if no tunnel is running. Removing a container while destructiveHint=false is not a contradiction, since container removal is not data destruction.

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 front-loaded sentence with the action verb first and zero filler. Nothing is redundant or padded.

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 one-parameter teardown tool with idempotent and non-destructive hints plus a fully described schema, the description covers what the tool does to the environment. The only real gap is not stating the state left behind for the profile, which the agent may care about before reconnecting.

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% and the single parameter is already documented as "Profile name from list_profiles." The description adds no meaning about the profile argument (e.g., case sensitivity or whether an unknown name errors), so the schema carries the load and baseline 3 applies.

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?

"Stops and removes the tunnel container for a profile" states a specific verb pair (stops, removes) and a specific resource (the tunnel container), which is far more precise than the tool name "disconnect" alone. It implicitly contrasts with connect but never names connect or another sibling to route the agent explicitly.

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?

There is no when-to-use or when-not-to-use guidance; the agent must infer that this is the teardown counterpart to connect. No prerequisites (e.g., must a tunnel be up first) or post-conditions are stated.

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