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

TableJSON 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 readOnlyHint=false and destructiveHint=false but are minimal. The description adds meaningful behavior beyond them: the action re-prices before submitting, saved_extras is the authoritative verification for what was actually saved, and client contact fields are mandatory inputs. It still omits idempotency, duplicate-request behavior, and error handling for a mutation tool.

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 core action, then follows with the critical constraints in a logical order. Slightly redundant in places (the empty-list rule is also in the schema description) and the emphasis marker formatting is informal, but every sentence carries operational value.

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-param, 9-required mutation tool with no output schema, the description covers the submission flow, data-entry rules, and the verification signal (saved_extras) an agent needs. The gap is the six optional scheduling/payment parameters, which are undocumented in both the schema and the description and could cause incorrect omissions.

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 67%, and the description goes beyond it for the highest-risk parameter: selected_extras must repeat every chosen extra with the exact id_opt and quantity because the preview stores nothing, and an empty list is valid only when no extras were selected. It also clarifies that name/email/phone are required data. The optional arrival/departure/currency/port-pay params receive no explanation in either place.

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 and resource ('Submits a request for a booking or a request for an option') and explicitly contrasts itself with the sibling booking_detail_mod as a stateless preview. An agent can distinguish this tool from the preview and from booking_detail 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 Guidelines4/5

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

Gives clear conditions and an alternative: booking_detail_mod is a preview and its selections are not stored, so this tool must be used to actually submit, and selected_extras must be repeated from that preview. It also mandates real client details and forbids guessing them. It does not, however, explain the booking-vs-option submission choice, which is left to the schema's mode param.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?