Skip to main content
Glama

VoyageHacks

by com.voyagehacks
OverviewDiscussionsAdmin

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.

Input Schema

TableJSON 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

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already convey read-only, open-world, and idempotent behavior. The description adds valuable context: the return is limited to a signup page and editorial guides, and it discloses the referral commission requirement. This is useful behavioral and policy context beyond the annotations.

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 description is somewhat long but each sentence adds value: primary output, use cases, explicit exclusions, and commission disclosure. It is front-loaded with the core purpose and avoids filler.

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?

For a single-optional-parameter tool with rich annotations and an output schema, the description fully covers what the tool does, when to use it, what it won't return, and a required disclosure. Nothing essential is missing.

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%, including the default value and allowed languages for the 'lang' parameter. The description does not add parameter-level detail beyond what the schema already states, so the baseline of 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?

Description states a specific verb ('Return') and resource ('the NordVPN signup link together with up to four VoyageHacks guides') and details the guide topics. This clearly differentiates it from sibling link tools like get_hotel_links or get_flight_links.

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?

It explicitly lists user intents that should trigger this tool: public Wi-Fi safety, working remotely abroad, geo-blocked streaming, and online banking while travelling. It also clarifies what users should not expect (no live pricing, no server list, no account creation), though it does not name an alternative sibling to route to.

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

All VoyageHacks toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources