Skip to main content
Glama
Sign In

Pixie Vacations Travel Booking

by io.github.Stevegriswoldatl
OverviewDiscussionsAdmin

get_sandals_beaches_deals

Get the current Sandals and Beaches sales (sale name, instant and air credit, book-by date) read live from sandals.com and beaches.com, plus this week's 777 suite deals, with Pixie Vacations booking URLs.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 behavioral burden. It usefully discloses that data is read live from sandals.com and beaches.com and is scoped to current/weekly deals, but it omits failure behavior, freshness guarantees, or whether booking URLs always accompany 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?

The description is a single, front-loaded sentence that packs the core purpose and returned fields efficiently. It is dense but readable; slightly more structure could improve it, but there is no filler.

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?

For a zero-parameter read tool with no output schema and no annotations, the description covers the essential outputs: sale name, instant and air credit, book-by date, weekly 777 suite deals, and booking URLs. It could say more about response structure or edge cases, but an agent can call it correctly from this definition.

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

Parameters4/5

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

The tool takes zero parameters, so there are no parameter semantics to explain; this establishes a baseline of 4. The description appropriately focuses on what the no-argument call returns rather than attempting parameter detail.

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 names a specific verb ('Get') and concrete resources: current Sandals and Beaches sales plus 777 suite deals. It enumerates returned fields (sale name, instant and air credit, book-by date) and the source sites, making the purpose clear, though it does not explicitly differentiate itself from sibling search tools like search_sandals_resorts.

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 implied by 'current sales' and 'this week's 777 suite deals', suggesting a promotions lookup. However, there is no explicit guidance on when to use this instead of search_sandals_resorts, search_beaches_resorts, or get_resort_booking_url, and no exclusions are stated.

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