Skip to main content
Glama
Sign In
vpnhop

vpnhop

by kylepantall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Remove a VPN profile

remove_profile
DestructiveIdempotent

Delete a saved VPN profile and its stored secrets, stop its tunnel, and require Touch ID confirmation to remove the configuration from vpnhop.

Instructions

Deletes a saved profile and its keyhop secrets (the user confirms with Touch ID), and stops its tunnel.

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": "remove_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileYesProfile name from list_profiles.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, yet the description still adds real value: it discloses that keyhop secrets are destroyed, that the tunnel is stopped as a side effect, and that an interactive Touch ID confirmation gates the call. It does not spell out irreversibility or failure behavior, keeping it just short of a 5.

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?

One front-loaded sentence with the destructive effect stated first and the secondary effects following. No filler, no restatement of the title.

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 destructive tool with annotations and no output schema, the description covers the key unknowns: what is destroyed, what else happens to the tunnel, and the confirmation gate. Only explicit irreversibility and error behavior are left unstated, which is minor given destructiveHint.

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% for the single 'profile' parameter, and the schema itself states it comes from list_profiles. The description adds no further meaning about the parameter, so the baseline of 3 applies since the schema does the work.

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 gives a specific verb and resource ('Deletes a saved profile') and enumerates the collateral effects (keyhop secrets removed, tunnel stopped), which implicitly separates it from save_profile and list_profiles. It stops short of explicitly naming a sibling that handles tunnel-only teardown, so it is clear but not fully differentiated.

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 statement of when to choose this tool over disconnect or save_profile, nor any exclusion such as 'use disconnect to stop a tunnel without deleting the profile.' The only context is an implied prerequisite that the user will be prompted for Touch ID, which is behavioral rather than usage guidance.

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