Skip to main content
Glama
Sign In
Lodgify MCP Server

Lodgify MCP Server

by Fast-Transients
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

create_booking

Create new vacation rental bookings in Lodgify by specifying property details, guest information, dates, and pricing.

Instructions

Create a new booking.

Args:
    property_id: The property ID for the booking
    room_type_id: The room type ID within the property
    arrival: Arrival date (YYYY-MM-DD)
    departure: Departure date (YYYY-MM-DD)
    guest_name: Guest's full name
    guest_email: Guest's email address
    guest_phone: Guest's phone number
    guest_country_code: Guest's country code (e.g., "US", "CA")
    people: Number of people (default: 2)
    total: Total booking amount (default: 0.0)
    currency_code: Currency code (default: "USD")
    status: Booking status (default: "Booked")
    source_text: Source description (default: "MCP API")

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "property_id": "<property_id>",
      "room_type_id": "<room_type_id>",
      "arrival": "<arrival>",
      "departure": "<departure>",
      "guest_name": "<guest_name>",
      "guest_email": "<guest_email>",
      "guest_phone": "<guest_phone>",
      "guest_country_code": "<guest_country_code>"
    },
    "name": "create_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
property_idYes
room_type_idYes
arrivalYes
departureYes
guest_nameYes
guest_emailYes
guest_phoneYes
guest_country_codeYes
peopleNo
totalNo
currency_codeNoUSD
statusNoBooked
source_textNoMCP API

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Create' implies a write operation, the description doesn't address critical aspects like required permissions, whether the operation is idempotent, error handling, or what happens on success/failure. For a mutation tool with 13 parameters, this leaves significant gaps in understanding its behavior.

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?

The description is well-structured with a clear purpose statement followed by a comprehensive parameter list. Every sentence serves a purpose, though the parameter explanations could be slightly more concise in places. The front-loaded purpose statement helps the agent quickly understand the tool's function.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (13 parameters, mutation operation) and lack of both annotations and output schema, the description is moderately complete. It excels at parameter semantics but lacks behavioral context, usage guidelines, and information about what the tool returns. For a creation tool with many parameters, more comprehensive guidance would be beneficial.

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?

The description provides excellent parameter semantics beyond the schema. For all 13 parameters, it adds meaningful explanations (e.g., 'Arrival date (YYYY-MM-DD)', 'Guest's full name', 'Currency code (default: "USD")') that clarify purpose and format. With 0% schema description coverage, this fully compensates and provides essential context the schema lacks.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with a specific verb ('Create') and resource ('booking'), making it immediately understandable. However, it doesn't differentiate this from sibling tools like 'update_booking_status' or explain how it relates to read operations like 'get_bookings', which prevents a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'update_booking_status' or how it relates to read operations. There's no mention of prerequisites, constraints, or typical use cases, leaving the agent to infer usage from context alone.

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

Deploy Server

Other Tools