Skip to main content
Glama

List VPN profiles

list_profiles
Read-only

Lists configured PassTunnel VPN profiles and their current state, returning ids for use as profile_id in other tools.

Instructions

Lists the VPN profiles configured in PassTunnel with their current state. Use the returned id as profile_id in the other tools. A profile with connect_refusal (code and message) is of a type this system cannot connect, such as Cisco AnyConnect or Palo Alto GlobalProtect on an older macOS; connect refuses it. experimental=true marks a profile of an experimental type (Palo Alto GlobalProtect). protected=true means connecting is refused on Linux for now (auth_unavailable): there is no confirmation to ask for yet.

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

Output Schema

NameRequiredDescriptionDefault
profilesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.8.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the description is not on the hook for the safety profile. It goes beyond them by explaining non-obvious outcomes: profiles carrying connect_refusal cannot be connected at all, experimental=true marks an experimental type, and protected=true means connecting is refused on Linux with auth_unavailable. It does not mention result size or whether the list is paginated/complete.

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 purpose and the profile_id hand-off are front-loaded in the first two sentences, with field semantics after. The remaining three flag explanations are dense but each covers a distinct refusal/experimental condition; a slightly terser phrasing could have grouped them, keeping it just short of ideal.

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

Completeness5/5

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

An output schema exists, so the description is not required to enumerate return fields, yet it explains the three values whose implications an agent could not infer (connect_refusal, experimental, protected). For a parameterless, read-only listing tool this covers everything needed to call it and act on the result.

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 no parameters, so the schema baseline is 4 and there is nothing for the description to compensate for. The description correctly spends its space on return-value interpretation instead of inventing parameter guidance.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Lists the VPN profiles configured in PassTunnel with their current state" gives a specific verb (lists) and resource (VPN profiles) plus a scope qualifier (current state). It also states the follow-up action for the returned id, so the agent immediately knows what this tool yields and where it fits, which cleanly separates it from siblings like get_status and get_logs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description tells the agent to call this first to obtain an id and pass it as profile_id to the other tools, which is concrete usage guidance. It does not state explicit exclusions or when another tool would be preferred, but for a zero-argument discovery tool the remaining guidance is minimal.

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