VoyageHacks

Search the VoyageHacks travel gear catalog

search_travel_gear

Read-onlyIdempotent

Search the VoyageHacks travel gear catalog: about 320 products that appear as picks in roughly 50 published buying guides, including carry-on backpacks, packing cubes and compression bags, universal travel adapters, GaN chargers, airline-compliant power banks, luggage trackers, neck pillows, earplugs and eye masks, toiletry and makeup bags, travel-size bottles, travel routers, translation earbuds and camping and outdoor gear. Each result returns the product name, its category, the published reason it was picked, the guide that reviews it, its Amazon ASIN and a link to the Amazon product page. Useful when a user asks which travel product to buy, or what to pack for a trip and names a category or a destination. For a whole kit built from a trip description rather than one category, recommend_travel_gear is the matching tool. This is the VoyageHacks editorial catalog, not a search of all of Amazon: products outside the published guides are not findable here, and prices, star ratings, review counts and stock are not available and are never returned. The Amazon links are affiliate links: VoyageHacks may earn a commission from qualifying purchases at no additional cost to the buyer, which should be disclosed when the links are presented.

Input Schema

TableJSON Schema

Name	Required	Description
`lang`	No	Language of the VoyageHacks guides returned. One of: en, de, fr, es, it, pl, cs, ja, nl, pt, zh. Defaults to "en".
`limit`	No	Maximum products to return. Defaults to 6.
`query`	Yes	What the traveler needs, e.g. "power bank for a long flight", "packing cubes", "adapter for Japan".

Output Schema

TableJSON Schema

Name	Required	Description	Default
`hub`	No
`lang`	Yes
`query`	Yes
`products`	Yes
`disclosure`	Yes
`productCount`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedAug 29, 2026

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\"."

changedInput schema / properties / limit / description

Previous value: -"Max products (default 6)"New value: +"Maximum products to return. Defaults to 6."

changedInput schema / properties / query / description

Previous value: -"What the traveler needs, e.g. \"power bank for a long flight\", \"packing cubes\", \"adapter for Japan\""New value: +"What the traveler needs, e.g. \"power bank for a long flight\", \"packing cubes\", \"adapter for Japan\"."

addedInput schema / properties / query / maxLength
```
Added value: +300
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "disclosure": {
+      "type": "string"
+    },
+    "hub": {
+      "type": "string"
+    },
+    "lang": {
+      "type": "string"
+    },
+    "productCount": {
+      "type": "integer"
+    },
+    "products": {
+      "items": {
+        "properties": {
+          "affiliate": {
+            "description": "True: the buy link is an affiliate link.",
+            "type": "boolean"
+          },
+          "asin": {
+            "type": "string"
+          },
+          "badge": {
+            "description": "Editorial label, e.g. \"Best overall\".",
+            "type": "string"
+          },
+          "buyUrl": {
+            "description": "Amazon product page, carrying the VoyageHacks Associates tag.",
+            "type": "string"
+          },
+          "category": {
+            "description": "Product category, taken from the buying guide it appears in.",
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "reviewGuide": {
+            "properties": {
+              "title": {
+                "type": "string"
+              },
+              "updated": {
+                "type": "string"
+              },
+              "url": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "title",
+              "url"
+            ],
+            "type": "object"
+          },
+          "source": {
+            "description": "Always \"amazon\".",
+            "type": "string"
+          },
+          "whyThisOne": {
+            "description": "The published reason this product was picked.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "asin",
+          "buyUrl",
+          "source",
+          "affiliate",
+          "reviewGuide"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "query": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "query",
+    "lang",
+    "products",
+    "disclosure"
+  ],
+  "type": "object"
+}

First observedAug 19, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already mark this as read-only, idempotent, and non-destructive, and the description adds valuable context on top of that: result fields, the editorial-catalog boundary, the absence of prices/ratings/review counts/stock, and the affiliate-link disclosure obligation. No contradiction with 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Every sentence in the description carries distinct information: catalog scope, result contents, intended use case, sibling alternative, limitations, and affiliate disclosure. It is front-loaded with the core action and scope, and the longer category list earns its place by conveying the breadth of the catalog.

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 tool with three documented parameters and an output schema, this description is complete: it states what results contain, what they never contain, what the catalog covers, and how links should be presented. An agent has all necessary context to invoke it correctly.

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%, so the parameters query, limit, and lang are already fully documented with examples and defaults. The description reinforces query semantics by mentioning category/destination queries but does not add significant new parameter-level detail, which is appropriate given the schema's coverage.

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 states a specific verb and resource ('Search the VoyageHacks travel gear catalog') and immediately clarifies the scope: roughly 320 products across about 50 published buying guides. It also distinguishes itself from the sibling recommend_travel_gear, making tool selection unambiguous.

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

Usage Guidelines5/5

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

The description explicitly says when to use this tool: when a user asks which travel product to buy or what to pack and names a category or destination. It also names the matching alternative for whole kits and states what the tool is not for (a general Amazon search), giving clear routing guidance.

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.