Skip to main content
Glama
panoskiriakopoulos-sys

Rizerve MCP Server

Create Rizerve Booking

rizerve_create_booking

Create a new booking for a property and block the calendar for the chosen dates. Requires property ID, guest name, check-in, check-out, and total price.

Instructions

Create a new booking for a property. Automatically blocks the calendar for the booked dates.

Required: property_id, guest_name, check_in, check_out, total_price (in cents). Returns 409 conflict if dates overlap with existing bookings.

Args:

  • property_id (string): Property UUID (required)

  • guest_name (string): Full guest name (required)

  • check_in (date): Check-in date YYYY-MM-DD (required)

  • check_out (date): Check-out date YYYY-MM-DD (required)

  • total_price (number): Total price in cents (required)

  • guest_email, guest_phone, guests, currency, payment_mode, notes (optional)

Returns: Created booking object with status "pending".

Examples:

  • "Book the villa for Maria, July 5-10, €750" → rizerve_create_booking({ property_id: "550e...", guest_name: "Maria P.", check_in: "2026-07-05", check_out: "2026-07-10", total_price: 75000 })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesNoInternal notes about this booking
guestsNoNumber of guests
check_inYesCheck-in date (YYYY-MM-DD)
check_outYesCheck-out date (YYYY-MM-DD)
guest_nameYesFull name of the guest
guest_emailNoGuest email address
guest_phoneNoGuest phone number
property_idYesProperty UUID
total_priceYesTotal price in euros (e.g. 750 = €750.00)
response_formatNoOutput format: 'markdown' or 'json'markdown
Behavior4/5

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

Discloses that calendar is automatically blocked and that overlapping dates cause a 409 conflict. Also mentions return object status 'pending'. No contradiction with annotations, which are minimal (non-idempotent, non-destructive).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is moderately concise but includes a full args list that repeats some schema info. Could be shortened without losing clarity.

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?

Covers required fields, conflict behavior, and return value (pending booking object). With no output schema, this is sufficient for an agent to understand what the tool does.

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

Parameters2/5

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

The description clarifies most parameters but contains a critical contradiction: description says total_price is 'in cents' while schema says 'in euros (e.g. 750 = €750.00)'. This inconsistency harms agent understanding.

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?

The description clearly states it creates a booking and blocks the calendar. It distinguishes from siblings like rizerve_block_date which blocks dates without a booking, and rizerve_list_bookings which only retrieves.

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?

The description lists required and optional parameters, mentions conflict behavior (409), and provides an example. However, it does not explicitly compare with sibling tools or state when not to use this tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/panoskiriakopoulos-sys/rizerve-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server