Skip to main content
Glama

Luxury Travel Tools by Global Lux Agency

Luxury packing list generator: yacht, safari, ski, cruise and beach

luxury-packing-list
Read-onlyIdempotent

Returns a packing checklist grouped into documents and money, clothing, footwear, toiletries, tech, health, activities, trip-type extras and children, with per-person quantities scaled to the nights and laundry (a planning choice). Trip types can be combined. Includes sourced UK cabin liquids rules and an example light-aircraft safari luggage limit. General guidance: no entry, visa or health advice; check airline and operator rules. Web page: https://globalluxagency.com/tools/luxury-packing-list

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": "luxury-packing-list"
  }
}

Input Schema

NameRequiredDescriptionDefault
skiNoTrip type: Ski or chalet. Combine as many as apply; with none, a city break is assumed.
spaNoActivity: Spa.
cityNoTrip type: City break. Combine as many as apply; with none, a city break is assumed.
golfNoActivity: Golf.
beachNoTrip type: Beach or resort. Combine as many as apply; with none, a city break is assumed.
yachtNoTrip type: Yacht charter. Combine as many as apply; with none, a city break is assumed.
adultsNoAdults travelling.
cruiseNoTrip type: Cruise. Combine as many as apply; with none, a city break is assumed.
divingNoActivity: Diving or snorkelling.
hikingNoActivity: Hiking or walking.
nightsNoNights away.
safariNoTrip type: Safari. Combine as many as apply; with none, a city break is assumed.
carryOnNoHand luggage only (caps clothes at 5 days).
climateNohot (25 °C+), mild (12–24 °C), cold (below 12 °C) or mixed.mild
laundryNoLaundry available (pack for a 4-day cycle).
weddingNoTrip type: Wedding or event. Combine as many as apply; with none, a city break is assumed.
blackTieNoActivity: Black-tie or formal evening.
businessNoTrip type: Business. Combine as many as apply; with none, a city break is assumed.
childrenNoChildren travelling (adds a per-child group).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. Beyond that, the description discloses genuinely additive behavior: quantities scale per person with nights and laundry treated as a planning choice, trip types combine, and the output embeds sourced UK cabin-liquids rules plus an example light-aircraft safari luggage limit. The disclaimer that it is general guidance rather than entry/visa/health advice is useful context an agent would not otherwise have.

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 output shape is front-loaded in the first sentence and the caveats follow in a short second block, so the agent hits the important information immediately. The enumeration of nine checklist groups is long but each item carries routing value, and the trailing URL is a minor appendage rather than waste.

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?

With 19 optional boolean/enum/integer parameters and no output schema, the description carries the burden of explaining what comes back — and it does, listing the grouping and the per-person scaling logic. It does not specify the response format (text vs. structured), which is the only real gap for a tool of this complexity.

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 every one of the 19 parameters carries its own description, including the 'combine as many as apply' note and the carry-on 5-day cap, so the schema does the work. The description restates the nights/laundry scaling and combinability but adds no syntax, format or defaulting insight beyond the schema — baseline 3 applies.

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 opens with a specific verb and resource — 'Returns a packing checklist' — and then enumerates the exact output groups (documents and money, clothing, footwear, toiletries, tech, health, activities, trip-type extras, children). That level of detail makes it unmistakably a content generator rather than any of the sibling calculators, without needing to name them.

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

Usage Guidelines3/5

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

Usage is only implied: 'Trip types can be combined' and the note that a city break is assumed if none are set tell the agent how to compose inputs, and 'no entry, visa or health advice; check airline and operator rules' draws a scope boundary. There is no explicit statement of when to reach for this tool versus siblings such as safari-planner or where-to-go-on-holiday-by-month, so the agent must infer the routing.

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.

Resources