Skip to main content
Glama
Frihet-io

Frihet MCP Server

by Frihet-io

Create Reservation

create_reservation

Create a new reservation manually by providing property ID, check-in and check-out dates, and guest count. Optionally include guest details or an existing guest ID.

Instructions

Create a new reservation manually (not via channel sync). Requires property ID, check-in/check-out dates, and guest count. Optionally provide a guest ID or inline guest data to create a new guest. / Crea una nueva reserva manualmente. Requiere propiedad, fechas y numero de huespedes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
guestNoNew guest data (used if guestId not provided) / Datos del nuevo huesped si no se proporciona guestId
notesNoInternal notes / Notas internas
checkInYesCheck-in date YYYY-MM-DD / Fecha de entrada
guestIdNoExisting guest ID (if known) / ID de huesped existente
checkOutYesCheck-out date YYYY-MM-DD / Fecha de salida
currencyNoISO 4217 currency (defaults to workspace currency) / Divisa
channelIdNoBooking channel ID (Airbnb, Booking.com, Direct) / Canal de reserva
guestCountYesNumber of guests / Numero de huespedes
propertyIdYesProperty ID / ID de propiedad
totalAmountNoTotal amount in workspace currency / Importe total

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
notesNo
nightsNo
statusYes
checkInYes
guestIdNo
checkOutYes
currencyNo
channelIdNo
createdAtNo
updatedAtNo
guestCountYes
propertyIdYes
totalAmountNo
Behavior3/5

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

Annotations declare no readOnly or destructive hints, and the description confirms it's a create operation. However, it does not disclose side effects like confirmation emails or immediate channel sync implications.

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

Conciseness5/5

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

Two concise sentences in English and one in Spanish, front-loaded with purpose, no redundant information.

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?

Given 10 parameters, nested objects, and output schema, the description covers the essentials but could mention what the tool returns (e.g., reservation ID) or date validation rules.

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 coverage is 100%, so baseline 3. The description adds minimal info beyond schema, only listing required fields and optional guest data, without further detail.

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 the verb 'Create', the resource 'reservation', and the context 'manually (not via channel sync)', distinguishing it from sibling tool sync_channel.

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?

Explicitly notes when to use (manual creation) and contrasts with channel sync, but does not mention when not to use or other alternatives like importing from channels.

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/Frihet-io/frihet-mcp'

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