Skip to main content
Glama
Sign In
vpnhop

vpnhop

by kylepantall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List VPN profiles

list_profiles
Read-only

Lists configured VPN profiles, including type, allowed hosts, and tunnel status, to help you inspect available tunnels before sending requests.

Instructions

Configured VPN profiles with their type, description, allowed hosts and whether each tunnel is up.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_profiles"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

readOnlyHint=true already declares the safe read profile, so the description's burden is lower; it adds that results cover configured profiles only and that connectivity state is included. It says nothing about ordering, pagination, or whether 'allowed hosts' can be large/nested, which are the remaining behavioral unknowns for a read tool.

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?

A single compact clause with no filler, and the most useful content (what is returned) comes first. The missing subject/verb makes it read as a fragment rather than a declarative sentence, a small clarity cost in otherwise tight wording.

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?

With no input schema, no output schema, and only readOnlyHint for annotations, the description must carry the return-shape burden — and it does list the per-profile fields. It is nearly complete for a trivial list tool; only ordering and volume characteristics are unstated.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter semantics to document and the baseline of 4 applies. The description does not need to compensate for any schema gaps here.

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 names the resource (configured VPN profiles) and enumerates what each entry contains: type, description, allowed hosts, and tunnel state. It is a noun-phrase fragment rather than a verb+resource statement, and it does not distinguish itself from the sibling 'status', which plausibly reports the same tunnel-up information.

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 call this versus the siblings (connect, disconnect, status, refresh). The listing behavior is implied by the field enumeration, but an agent gets no explicit trigger condition or exclusion, and the overlap with 'status' is left unresolved.

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