Skip to main content
Glama

Search available yachts

search_boats
Read-onlyIdempotent

Search Sedna for yachts available for the exact requested dates.

Call Base_list first and use an official base name. Results have passed Sedna planning/block and pricing checks for start_date plus nights. If more than 30 yachts match, state the accurate count and ask for a fleet, model or year preference. If 30 or fewer match, show every result with its fleet name; never select an arbitrary subset. If none match, offer alternative bases or dates.

Search results intentionally contain no yacht images. If the customer asks to see photos, a gallery, plans, videos or documents for a selected yacht, call boat_details with its exact id_boat and display the returned public media URLs. Use booking_detail for date-specific prices, extras, ports and booking choices.

Length and beam are optional fleet-supplied facts. Missing values are omitted and must never exclude an otherwise matching yacht, be shown as zero, be estimated, or trigger a clarification unless the customer has explicitly made that dimension a requirement.

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": {
      "base": "<base>",
      "start_date": "<start_date>",
      "nights": "<nights>"
    },
    "name": "search_boats"
  }
}

Input Schema

NameRequiredDescriptionDefault
paxNoOptional passenger-capacity filter. A single number means at least that many guests; ranges and comparators are also supported.
baseYesExact base name returned by Base_list.
pageNoResult page starting at 1.
priceNoOptional price filter in the currency returned by Sedna.
nightsYesNumber of charter nights.
optionNoAdditional supported Sedna filters.
bathroomNoOptional bathroom filter.
boat_typeNoOptional exact yacht type.
boat_yearNoOptional build-year filter (exact, range or comparator).
boat_modelNoOptional yacht brand, partial model or complete model. For example, "Lagoon" matches Lagoon 380, Lagoon 40 and Lagoon 42; "Lagoon 42" also matches directly.
fleet_nameNoOptional fleet preference.
start_dateYesFuture charter start date in YYYY-MM-DD format.
double_cabinNoOptional double-cabin filter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / boat_model / description
      Previous value: -"Optional yacht model."New value: +"Optional yacht brand, partial model or complete model. For example, \"Lagoon\" matches Lagoon 380, Lagoon 40 and Lagoon 42; \"Lagoon 42\" also matches directly."
  2. Changed1 schema field changed
    • changedInput schema / properties / pax / description
      Previous value: -"Optional passenger filter (exact, range or comparator)."New value: +"Optional passenger-capacity filter. A single number means at least that many guests; ranges and comparators are also supported."
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, but the description adds substantial behavioral context beyond them: results are pre-validated against planning/block and pricing checks, images are intentionally omitted, and the 30-result threshold governs whether to paginate/broaden or present everything. The length/beam rule (missing values omitted, never zero, never estimated, never a clarification trigger) is unusually concrete guidance for edge-case handling.

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 opening sentence front-loads the core purpose and calls, and each subsequent paragraph handles a distinct concern (prerequisite, result-count rules, media handoff, missing dimensions) rather than repeating the schema. It runs long for a search tool, but no sentence is filler; minor tightening is possible in the sibling-handoff paragraph.

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?

With 13 parameters, no output schema, and no enum constraints, the description compensates by explaining what results contain (no images), what they are validated for, how to handle result volume, and how missing dimensions are represented. An agent has everything needed to call this correctly and interpret the response without guessing.

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 carries parameter documentation and the baseline is 3. The description contributes only the constraint that base must be an official Base_list name and that start_date plus nights define the availability window; the remaining 10 optional filters get no treatment in the description. Useful but marginal on top of a fully documented schema.

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?

"Search Sedna for yachts available for the exact requested dates" gives a specific verb, resource, and scope, and the availability-plus-pricing-check framing separates it from compare_boats and boat_details. An agent can tell immediately that this is the availability search entry point, not a detail or comparison tool.

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

Usage Guidelines5/5

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

The description names prerequisites (call Base_list first, use an official base name) and routes to siblings with explicit conditions: boat_details for photos/plans/documents, booking_detail for date-specific prices and extras. It also branches by result count (>30 ask for a preference, <=30 show all, zero offer alternative bases or dates), which is exactly the when-to-use guidance an agent needs.

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