Skip to main content
Glama

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, its Amazon ASIN and a link to the product on the VoyageHacks buying guide that reviews it, where it can be bought on Amazon. Useful when a user asks which travel product to buy, or what to pack for a trip and names a category or a destination. 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 guides carry Amazon affiliate links: VoyageHacks may earn a commission from qualifying purchases at no additional cost to the buyer, which should be disclosed when the products are presented.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_travel_gear"
  }
}

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".
limitNoMaximum products to return. Defaults to 6.
queryYesWhat the traveler needs, e.g. "power bank for a long flight", "packing cubes", "adapter for Japan".

Output Schema

NameRequiredDescriptionDefault
hubNo
langYes
queryYes
productsYes
disclosureYes
productCountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • removedOutput schema / properties / products / items / properties / affiliate
      Removed value: -{
      -  "description": "True: the buy link is an affiliate link.",
      -  "type": "boolean"
      -}
    • removedOutput schema / properties / products / items / properties / buyUrl
      Removed value: -{
      -  "description": "Amazon product page, carrying the VoyageHacks Associates tag.",
      -  "type": "string"
      -}
    • addedOutput schema / properties / products / items / properties / productUrl
      Added value: +{
      +  "description": "The product on its VoyageHacks buying guide (#p-<asin>), where the Amazon buy button is.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / products / items / properties / retailer
      Added value: +{
      +  "description": "Where the product is sold. Always \"Amazon\".",
      +  "type": "string"
      +}
    • removedOutput schema / properties / products / items / properties / source
      Removed value: -{
      -  "description": "Always \"amazon\".",
      -  "type": "string"
      -}
    • changedOutput schema / properties / products / items / required
      Previous value: -[
      -  "name",
      -  "asin",
      -  "buyUrl",
      -  "source",
      -  "affiliate",
      -  "reviewGuide"
      -]New value: +[
      +  "name",
      +  "asin",
      +  "productUrl",
      +  "retailer",
      +  "reviewGuide"
      +]
  2. 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"
      +]
  3. Changed5 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\"."
    • 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"
      +}
  4. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint), yet the description adds substantial context beyond them: exactly what each result contains (name, category, published pick reason, ASIN, guide link), what is never returned (prices, star ratings, review counts, stock), and a mandatory affiliate-disclosure obligation when presenting results.

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?

Front-loaded with the catalog scope, then results, then caveats, then the affiliate note — a sensible ordering with no filler sentences. The long enumeration of product categories (carry-on backpacks through camping gear) is somewhat bloated and could be trimmed, but it does communicate query coverage.

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 three-parameter, read-only search with full schema coverage, open-world annotations and an output schema, the description covers everything an agent needs: catalog scope, when to invoke, what is returned, what is unavailable, and the disclosure requirement. Return fields are restated despite the output schema, which is mild redundancy rather than a gap.

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 schema already documents query, limit (1-12, default 6) and lang (enum with default). The description adds no parameter-level guidance of its own — its example queries and result-field list duplicate what the schema conveys. Baseline 3 applies when the schema does the heavy lifting.

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

Purpose4/5

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

States a specific verb and resource ('Search the VoyageHacks travel gear catalog') and pins the scope precisely: ~320 products from ~50 published guides, with product categories enumerated. It explicitly distinguishes itself from an all-of-Amazon search, but never mentions the sibling tool recommend_travel_gear, which is the most plausible confusion point for an agent choosing between the two.

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 a clear trigger: 'Useful when a user asks which travel product to buy, or what to pack for a trip and names a category or a destination.' It also states an exclusion in the form of scope limits (products outside the published guides are not findable, no prices/ratings/stock). What is missing is an explicit alternative — recommend_travel_gear is not named as the tool to use when a specific query is not appropriate.

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.