Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
LODGIFY_API_KEYYesThe API key for the Lodgify vacation rental API.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_propertiesC
Get a list of properties with optional filtering.

Args:
    limit: Maximum number of properties to return (default: 50)
    offset: Number of properties to skip (default: 0)
    status: Filter by property status (e.g., "Active", "Inactive")
get_property_by_idC
Get detailed information about a specific property.

Args:
    property_id: The unique ID of the property
get_bookingsB
Get bookings with optional filtering.

Args:
    size: Maximum number of bookings to return
    page: Number of page to get
    property_id: Filter by specific property ID
    status: Filter by booking status (e.g., "Booked", "Cancelled")
    start_date: Filter bookings from this date (YYYY-MM-DD)
end_date: Filter bookings until this date (YYYY-MM-DD)
create_bookingB
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")
get_calendarB
Get calendar/availability information for a property.

Args:
    property_id: The property ID
    room_type_id: Optional room type ID within the property
    start_date: Start date for calendar (YYYY-MM-DD)
    end_date: End date for calendar (YYYY-MM-DD)
get_booking_by_idC
Get detailed information about a specific booking.

Args:
    booking_id: The unique ID of the booking
update_booking_statusB
Update the status of an existing booking.

Args:
    booking_id: The unique ID of the booking
    status: New status (e.g., "Booked", "Cancelled", "CheckedIn", "CheckedOut")
get_occupancy_summaryB
Get occupancy summary, average rental rate, and total revenue for a property
within a specified date range.

Args:
    property_id: The property ID
    start_date: Start date for analysis (YYYY-MM-DD)
    end_date: End date for analysis (YYYY-MM-DD)

Prompts

Interactive templates invoked by user choice

NameDescription
analyze_lodgify_dataAnalyze Lodgify property and booking data for insights.
analyze_occupancy_data_prompt Analyze occupancy data for a specific property and date range.
create_booking_workflowGuide through creating a new booking in Lodgify.
property_management_reviewReview property management and booking status.

Resources

Contextual data attached and managed by the client

NameDescription
get_properties_listGet a summary list of all properties.
get_recent_bookingsGet recent bookings summary.

TDQS

A3.5/5.0

Scored across 8 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no ambiguity. The tools cover different aspects of the Lodgify domain: booking creation, retrieval, status updates, property management, calendar/availability, and occupancy analysis. There is no overlap in functionality between tools like get_booking_by_id, get_bookings, and update_booking_status.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with snake_case throughout. The naming convention is predictable: create_booking, get_booking_by_id, get_bookings, get_calendar, get_occupancy_summary, get_properties, get_property_by_id, update_booking_status. This consistency makes it easy for agents to understand and select the appropriate tool.

Tool Count5/5

With 8 tools, this server is well-scoped for property management and booking operations. Each tool earns its place by covering essential CRUD operations for bookings and properties, plus additional utilities like calendar and occupancy analysis. The count is neither too thin nor too heavy for the domain.

Completeness4/5

The tool surface provides strong coverage for core booking and property management workflows, including create, read, and update operations. Minor gaps exist, such as no delete_booking or update_property tools, but agents can work around these with the available status updates and property retrieval. The inclusion of calendar and occupancy tools adds valuable domain-specific functionality.

Maintenance

ActivityInactive
ResponsivenessNo issues