Skip to main content
Glama
Sign In

Pixie Vacations Travel Booking

by io.github.Stevegriswoldatl
OverviewDiscussionsAdmin

search_virgin_voyages

Search Virgin Voyages adult-only cruises (18+, no kids). Returns ship info (Scarlet Lady, Valiant Lady, Resilient Lady, Brilliant Lady), regions sailed, what's included (Wi-Fi, gratuities, basic dining, group fitness), and a Pixie Vacations booking URL. Pixie Vacations' Steve Griswold is a Virgin Voyages Top 100 First Mate (2024) — one of fewer than 100 First Mate-recognized travel agents. Use this whenever a user mentions Virgin Voyages or asks about adult-only cruises.

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": "search_virgin_voyages"
  }
}

Input Schema

NameRequiredDescriptionDefault
shipNoScarlet Lady, Valiant Lady, Resilient Lady, or Brilliant Lady
regionNoCaribbean, Mediterranean, Greek Isles, Australia, Bermuda, Transatlantic, etc.
departure_monthNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that results include ship info, regions sailed, inclusions, and a booking URL, but it does not clarify whether it returns actual sailings versus general information, nor does it mention pagination or result-completeness traits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The primary purpose is front-loaded, but the paragraph about Pixie Vacations and Steve Griswold's Top 100 First Mate status is promotional rather than invocation-relevant. It is not excessively long, but some sentences do not earn their place for an agent choosing a tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a search tool with three optional parameters and no output schema, the description reasonably explains the return contents. It still leaves gaps around how it differs from find_cruise and how departure_month affects results, which matters for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 67% description coverage, leaving departure_month undocumented. The description repeats ship names and region concepts already in the schema but adds no syntax, format, or filtering semantics, so it does not compensate for the uncovered parameter.

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?

The description states a specific verb and resource: searching Virgin Voyages adult-only cruises, with a clear 18+ scope. It also names the ships and included amenities returned. It does not explicitly distinguish itself from the sibling find_cruise tool, so it falls short of a 5.

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 a clear use condition: whenever a user mentions Virgin Voyages or asks about adult-only cruises. However, it does not name alternatives such as find_cruise or state when not to use this tool, so it lacks full routing guidance.

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

All Pixie Vacations Travel Booking 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