VoyageHacks

Get travel eSIM links for a destination

get_esim_links

Read-onlyIdempotent

Return travel eSIM store links (Airalo, covering 200+ countries, plus Yesim, Saily and Drimsim) together with up to four VoyageHacks eSIM guides for that destination covering real per-GB prices, coverage, setup steps and which phones support eSIM. Useful when a user asks about mobile data abroad, SIM cards, roaming charges, staying online on a trip or tethering a laptop. It returns store pages: no live plan prices, no coverage check for a specific handset, and no purchase or activation. Affiliate links: VoyageHacks may earn a commission at no additional cost to the traveler, which should be disclosed when the links are presented.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`lang`	No	Language of the VoyageHacks guides returned. One of: en, de, fr, es, it, pl, cs, ja, nl, pt, zh. Defaults to "en".
`destination`	No	Country or region the data plan is for, e.g. Japan, Europe, USA.

Output Schema

TableJSON Schema

Name	Required	Description
`guides`	Yes	Matching VoyageHacks guides that can be cited as sources.
`providers`	Yes
`disclosure`	Yes
`destination`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedAug 29, 2026

changedInput schema / properties / destination / description

Previous value: -"Country or region the data is for, e.g. Japan, Europe, USA"New value: +"Country or region the data plan is for, e.g. Japan, Europe, USA."

addedInput schema / properties / destination / maxLength
```
Added value: +120
```

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": {
+    "destination": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "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"
+    },
+    "providers": {
+      "items": {
+        "properties": {
+          "label": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "label",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "disclosure",
+    "providers",
+    "guides"
+  ],
+  "type": "object"
+}

First observedAug 19, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already mark this as read-only and idempotent, so the description's disclosures go beyond them: it returns store pages, not live pricing, cannot check specific handsets, and cannot purchase/activate. It also transparently discloses the affiliate commission and the need to mention it, which is valuable behavioral context.

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?

Each sentence earns its place: core output, intended use cases, limitations, and affiliate disclosure. The description is structured front-loaded with the main purpose and stays reasonably compact for the amount of context it conveys.

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 read-only link-returning tool with annotations and an output schema, the description is complete. It covers what is returned, what is not returned, when to use it, and a required disclosure policy.

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 both parameters, so the schema already documents 'lang' and 'destination' clearly. The description adds little parameter-specific meaning, 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?

The description specifies a clear action ('Return') and resource ('travel eSIM store links... plus VoyageHacks eSIM guides'). It differentiates from sibling link tools by focusing on eSIM specifically and listing the exact stores covered.

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 gives explicit use cases: 'when a user asks about mobile data abroad, SIM cards, roaming charges...' and states limitations like 'no live plan prices, no coverage check... no purchase or activation.' It does not name a specific sibling alternative, so it stops short of a perfect 5.

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

All VoyageHacks tools Inspect

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.