Skip to main content
Glama

Get travel VPN links

get_travel_vpn_links
Read-onlyIdempotent

Return the NordVPN signup link together with up to four VoyageHacks guides on whether a traveler actually needs a VPN, the real risks of hotel and airport Wi-Fi, and watching home streaming services abroad. Useful when a user raises public Wi-Fi safety, working remotely abroad, geo-blocked streaming or online banking while travelling. It returns a signup page and editorial guides: no live pricing, no server list and no account creation. Referral link: VoyageHacks may earn a commission at no additional cost to the user, which should be disclosed when the link is presented.

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

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the VoyageHacks guides returned. One of: en, de, fr, es, it, pl, cs, ja, nl, pt, zh. Defaults to "en".

Output Schema

NameRequiredDescriptionDefault
vpnYes
guidesYesMatching VoyageHacks guides that can be cited as sources.
disclosureYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / lang / enum
      Previous value: -[
      -  "en",
      -  "de",
      -  "fr",
      -  "es",
      -  "it",
      -  "pl",
      -  "cs",
      -  "ja",
      -  "nl",
      -  "pt",
      -  "zh"
      -]New value: +[
      +  "en",
      +  "de",
      +  "fr",
      +  "es",
      +  "it",
      +  "pl",
      +  "ja",
      +  "nl",
      +  "pt",
      +  "zh"
      +]
  2. Changed2 schema fields changed
    • changedInput schema / properties / lang / description
      Previous value: -"Content language for the guides that come back (default \"en\")"New value: +"Language of the VoyageHacks guides returned. One of: en, de, fr, es, it, pl, cs, ja, nl, pt, zh. Defaults to \"en\"."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "disclosure": {
      +      "type": "string"
      +    },
      +    "guides": {
      +      "description": "Matching VoyageHacks guides that can be cited as sources.",
      +      "items": {
      +        "properties": {
      +          "section": {
      +            "type": "string"
      +          },
      +          "title": {
      +            "type": "string"
      +          },
      +          "url": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "title",
      +          "url"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "vpn": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "disclosure",
      +    "vpn",
      +    "guides"
      +  ],
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent and non-destructive, so the safety profile is covered. The description adds real value beyond that: it bounds expectations ('no live pricing, no server list and no account creation') and surfaces an obligation not present in any structured field (the referral commission that must be disclosed when the link is presented).

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 return contents and usage triggers are front-loaded and every sentence carries information; the only mild bloat is the run-on middle sentence listing topics. No filler or repetition of the schema.

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?

An output schema exists, so return values need not be explained, and the description still covers scope, triggers, and the disclosure caveat. Missing only edge details like whether guides are localized per the lang argument, which is otherwise handled by the schema.

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 description coverage is 100% and the schema fully documents the single 'lang' enum with its default, so the description adds no parameter meaning. Baseline 3 is appropriate.

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?

States a specific verb and resource ('Return the NordVPN signup link together with up to four VoyageHacks guides') and enumerates the exact content topics, so the agent can distinguish it from the other get_*_links siblings without opening any schema.

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?

Gives explicit trigger conditions ('when a user raises public Wi-Fi safety, working remotely abroad, geo-blocked streaming or online banking while travelling'), which tells the agent when to reach for this tool. It does not name an alternative sibling or state when NOT to use it, so it stops short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.