Skip to main content
Glama
Sign In

Aisle

by wedding.aisle
OverviewDiscussionsAdmin

Guest Travel Estimator

get_guest_travel_estimate
Read-onlyIdempotent

Estimates round-trip flights and lodging in USD for guest groups departing from supported US metros. Stay length and guests per room can be set, and default to the destination’s typical stay in a private room per guest. Each priced group gives a typical figure and a low-to-high range. Partial totals include only priced groups; unpriced guests and unsupported origins are reported separately. The urlRestoresEstimate field states whether the returned web link restores the supplied groups. Estimates are not live fares or bookings.

Input Schema

NameRequiredDescriptionDefault
groupsNoGuest groups by departure city
nightsNoNights in the room, 1 to 30. Defaults to the destination's typical stay, shown as typicalStayNights on each group.
destinationNoDestination slug. Supported: algarve, amalfi-coast, argentina, aruba, aspen, bahamas, bali, barbados, barcelona, bermuda, cabo, cancun, cape-town, capri, charleston, cinque-terre, colombia, costa-rica, cotswolds, dominican-republic, dubrovnik, fiji, hawaii, iceland, ireland, jamaica, japan, kenya, lake-como, maldives, mallorca, maui, montenegro, morocco, mykonos, napa-valley, new-zealand, paris, peru, provence, puerto-rico, punta-cana, ravello, santorini, savannah, scottish-highlands, sorrento, sri-lanka, st-lucia, swiss-alps, thailand, dolomites, tulum, turks-and-caicos, tuscany, us-virgin-islands, vietnam.
guests_per_roomNoGuests sharing each room, 1 to 4. Defaults to 1, a private room per guest; 2 prices couples sharing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / guests_per_room
      Added value: +{
+  "description": "Guests sharing each room, 1 to 4. Defaults to 1, a private room per guest; 2 prices couples sharing.",
+  "maximum": 4,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / nights
      Added value: +{
+  "description": "Nights in the room, 1 to 30. Defaults to the destination's typical stay, shown as typicalStayNights on each group.",
+  "maximum": 30,
+  "minimum": 1,
+  "type": "integer"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / destination / description
      Previous value: -"Destination slug. Supported: algarve, amalfi-coast, aspen, bahamas, bali, barcelona, cabo, cancun, cape-town, capri, charleston, cinque-terre, cotswolds, dominican-republic, hawaii, lake-como, mallorca, maui, mykonos, napa-valley, paris, provence, puerto-rico, punta-cana, ravello, santorini, savannah, scottish-highlands, sorrento, thailand, dolomites, tulum, tuscany, us-virgin-islands."New value: +"Destination slug. Supported: algarve, amalfi-coast, argentina, aruba, aspen, bahamas, bali, barbados, barcelona, bermuda, cabo, cancun, cape-town, capri, charleston, cinque-terre, colombia, costa-rica, cotswolds, dominican-republic, dubrovnik, fiji, hawaii, iceland, ireland, jamaica, japan, kenya, lake-como, maldives, mallorca, maui, montenegro, morocco, mykonos, napa-valley, new-zealand, paris, peru, provence, puerto-rico, punta-cana, ravello, santorini, savannah, scottish-highlands, sorrento, sri-lanka, st-lucia, swiss-alps, thailand, dolomites, tulum, turks-and-caicos, tuscany, us-virgin-islands, vietnam."
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), but the description adds real behavioral detail: partial totals include only priced groups, unpriced guests and unsupported origins are reported separately, and urlRestoresEstimate signals whether the link preserves the supplied groups. It does not describe pagination or caching, but for an estimate endpoint this is substantial added context.

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?

Five short sentences, each earning its place, front-loaded with the core purpose before edge-case behavior. Slightly dense but no wasted phrasing.

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 read-only estimation tool with no output schema, the description covers return semantics (typical figure, low-to-high range), partial-result behavior, the urlRestoresEstimate field, and the non-live-fare caveat. Nothing essential for correct invocation is missing.

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?

Schema coverage is 100% (baseline 3), and the description further clarifies defaults: stay length and guests-per-room default to the destination's typical stay in a private room per guest, with guests_per_room=2 pricing couples sharing. This adds meaning beyond the schema's 'default 1' wording.

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?

States a specific verb (estimates) and resource (round-trip flights + lodging for guest groups from US metros), with a clear currency/scope (USD). An agent can separate it from siblings like get_budget_estimate or get_alcohol_estimate without opening the schema.

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?

The description implies usage (price travel for guest groups) and adds a useful scope disclaimer ('not live fares or bookings'), but it never states when to use this vs. the other estimate/suggestion tools such as get_budget_estimate. No explicit alternatives or exclusions beyond the disclaimer.

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

All Aisle 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