Sedna Genesis

compare_boats

Read-onlyIdempotent

Compare 2 to 4 boats using Sedna's date-specific customer pricing.

boat_ids: list of 2..4 boat ids
pax: customer passenger count used by booking_detail pricing
currency: EUR, USD, CNY (default EUR)
start_date/end_date: optional availability window (YYYY-MM-DD)

For dated comparisons, customer_cost_summary clearly separates charter price, mandatory extras, full customer cost and refundable deposit. The full customer cost comes from the same booking preview as booking_detail; the refundable deposit is always separate. Cabin fields explicitly label total, double, single and bunk cabins.

Length and beam are optional fleet-supplied facts. Missing values are omitted rather than returned as zero/null or estimated, and must not make an otherwise valid yacht unavailable for comparison.

Input Schema

Name	Required	Default
`pax`	Yes
`boat_ids`	Yes
`currency`	No	EUR
`end_date`	No
`start_date`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 29, 2026

addedInput schema / properties / pax
```
Added value: +{
+  "type": "integer"
+}
```

changedInput schema / required

Previous value: -[
-  "boat_ids"
-]New value: +[
+  "boat_ids",
+  "pax"
+]

First observedSep 10, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive, so safety is covered. The description adds genuinely non-obvious behavior: deposits are always reported separately from full customer cost, and missing length/beam are omitted rather than zeroed, nulled or estimated, explicitly without affecting availability.

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?

Front-loads the one-line purpose, then a scannable parameter list, then output semantics. Every sentence is substantive, though the second paragraph drifts into return-value detail that the output schema already covers and could be trimmed.

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 annotations covering the safety profile and an output schema present, the definition supplies enough to call the tool correctly for a comparison query. Only edge behavior (invalid/duplicate ids, currency unsupported, date range without pricing) is left unaddressed.

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

Parameters5/5

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

Schema coverage is 0%, so the description carries the full burden and does: it gives the 2..4 bound on boat_ids (absent from the schema), explains that pax feeds booking_detail pricing, enumerates the currency values EUR/USD/CNY with the EUR default, and fixes the date format as YYYY-MM-DD.

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?

Opens with a specific verb+resource+scope: 'Compare 2 to 4 boats using Sedna's date-specific customer pricing.' That framing inherently separates it from search_boats (discovery) and boat_details (single yacht), and it further anchors itself by referencing the booking_detail pricing it mirrors.

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?

Conveys the operating context (2-4 boats, optional date window, dated vs undated comparisons) and ties output to booking_detail's preview, but never states when to prefer this over search_boats or boat_details, nor any exclusions or error conditions such as fewer than 2 or more than 4 ids.

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

All Sedna Genesis tools Inspect

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

Need Help?