Sedna Genesis

booking_create

Submits a request for a booking or a request for an option.

This action re-prices and submits the request. booking_detail_mod is a stateless preview: selections made there are not stored automatically. Therefore selected_extras MUST repeat every extra the customer selected, using the exact id_opt and quantity. Pass an empty list only when the customer selected no optional extras. Never report an extra as selected unless this tool's saved_extras verification confirms it.

Full client details (name, email, phone) are required to submit the request. **** strong rule: AI should not guess or input customer information on its own. It must ask customers to input it on its own.

Input Schema

Name	Required	Description	Default
`pax`	Yes	Number of passengers.
`mode`	No	The type of creation, 'booking' or 'option' (defaults to 'booking').	booking
`dateEnd`	Yes	The end date (DD/MM/YYYY).
`id_boat`	Yes	The unique boat identifier.
`id_tbf1`	Yes	The TBF1 identifier for the booking.
`dateStart`	Yes	The start date (DD/MM/YYYY).
`client_name`	Yes	The client's full name.
`client_email`	Yes	The client's valid email address.
`client_phone`	Yes	The client's contact phone number.
`selected_extras`	Yes	Required complete selection. Example: [{"id_opt": 123, "selected": true, "quantity": 1}]. Use [] only when no optional extra was selected.
`arrival_selected`	No
`currency_id_devise`	No
`departure_selected`	No
`arrival_port_pay_option`	No
`departure_port_pay_option`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedSep 11, 2026

removedInput schema / properties / selected_extras / anyOf

Removed value: -[
-  {
-    "items": {
-      "additionalProperties": true,
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / selected_extras / default
```
Removed value: -null
```

addedInput schema / properties / selected_extras / description

Added value: +"Required complete selection. Example:\n[{\"id_opt\": 123, \"selected\": true, \"quantity\": 1}].\nUse [] only when no optional extra was selected."

addedInput schema / properties / selected_extras / items

Added value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

addedInput schema / properties / selected_extras / type
```
Added value: +"array"
```

changedInput schema / required

Previous value: -[
-  "client_name",
-  "client_email",
-  "client_phone",
-  "id_tbf1",
-  "id_boat",
-  "dateStart",
-  "dateEnd",
-  "pax"
-]New value: +[
+  "client_name",
+  "client_email",
+  "client_phone",
+  "id_tbf1",
+  "id_boat",
+  "dateStart",
+  "dateEnd",
+  "pax",
+  "selected_extras"
+]

First observedSep 10, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations declare the safety profile (not read-only, open-world, non-idempotent, not destructive), and the description adds genuinely non-obvious behavior: the call re-prices, saved_extras verification is the source of truth for what was actually selected, full client details are mandatory, and the AI must not fabricate customer information. These are meaningful additions beyond the annotations, though the consequence of the non-idempotent re-submit is not spelled out.

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?

Content is front-loaded with purpose, then the critical selected_extras rule, then the client-detail rule. Most sentences earn their place, but the trailing bolded rule with stray formatting markers ('**** strong rule') and inline quotes is untidy and slightly redundant with the client-details sentence above it.

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 15-parameter mutation tool with no output schema, the description covers the two highest-risk requirements (complete extras, real client data) and the preview-vs-submit distinction. It leaves the optional arrival/departure/currency/port-pay parameters and the saved_extras verification field unexplained, but no critical calling detail 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?

With schema coverage at 67% and 15 parameters, the schema documents the primitives but the description adds real semantics for the highest-risk field: selected_extras must repeat every extra with exact id_opt and quantity, and [] is valid only when nothing was chosen. It also reinforces that client_name/email/phone are required. The four pagination/currency/port-pay optional parameters are left unexplained in both places.

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 ('submits a request') and both resources ('booking' or 'option'), and explicitly contrasts itself with the sibling booking_detail_mod, which is a stateless preview. An agent can distinguish this from booking_detail and booking_detail_mod without opening any schema.

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?

Gives clear context for use: this is the tool that persists and re-prices, whereas booking_detail_mod does not store selections, and it names the alternative explicitly. It does not spell out when to pick 'option' mode over 'booking' mode, but the mode parameter plus default covers that gap.

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?