Skip to main content
Glama

lilo Vacation Rentals

by io.github.lilo-property

book_vacation_rental_direct

Destructive

Book a vacation rental property directly through AI. Host receives 100% of nightly rate; 3% guest service fee added at checkout. Creates booking record, calculates pricing, and notifies the host. Returns booking_id, confirmation_code, pricing breakdown, and check-in link. Always call check_vacation_rental_availability_and_pricing first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
guest_nameYesName of the guest
guest_countNoNumber of guests (default 1)
guest_emailYesGuest email address
guest_phoneNoGuest phone number
property_idYesProperty UUID or lilo_code
check_in_dateYesCheck-in date (YYYY-MM-DD)
check_out_dateYesCheck-out date (YYYY-MM-DD)
special_requestsNoAny special requests from guest

TDQS

A4.4/5.0
Behavior4/5

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

Annotations indicate readOnly=false and destructiveHint=true, but the description adds meaningful side effects: it creates a booking record, calculates pricing, notifies the host, and adds a 3% guest service fee. It stops short of discussing cancellation or refund behavior, but still adds value beyond the annotations.

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?

Four compact sentences cover purpose, pricing transparency, side effects, return values, and a required prerequisite. There is no filler; every sentence contributes essential 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?

For an 8-parameter mutation tool with no output schema, the description provides expected return fields (booking_id, confirmation_code, pricing breakdown, check-in link) and a required preceding call. It could mention cancellation/error handling, but schema richness and annotations cover most missing context.

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 description coverage is 100%, so the description does not need to re-document parameters. The description adds no parameter-specific details beyond the schema, but it does mention pricing calculation and the required prerequisite, which indirectly supports parameter usage.

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 opens with a direct verb ('Book') and a specific resource ('vacation rental property'), with the qualifier 'directly through AI.' It clearly distinguishes this from sibling risk/availability tools by stating it creates a booking record and returns confirmation artifacts.

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

Usage Guidelines5/5

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

The description explicitly instructs 'Always call check_vacation_rental_availability_and_pricing first,' giving a clear precondition. It also communicates the direct-booking context and fee structure, which signals when this tool is appropriate versus search or risk-assessment alternatives.

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

All lilo Vacation Rentals toolsInspect
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.

TDQS

A3.6/5.0
Disambiguation2/5

There is significant overlap and redundancy among tools, causing ambiguity. For example, analyze_booking_threat_risk, analyze_guest_communication_risk, and analyze_guest_interaction_risk are aliases or near-duplicates, and multiple tools like get_vacation_rental_details and fetch_vacation_rental_details appear to serve the same purpose. This makes it difficult for an agent to choose the correct tool without confusion.

Naming Consistency4/5

Most tools follow a consistent verb_noun pattern (e.g., check_vacation_rental_availability_and_pricing, get_vacation_rental_details), which aids readability. However, there are minor deviations, such as some tools using 'analyze' vs. 'assess' or 'detect' for similar risk functions, and a few tools like 'ingest_philadelphia_public_records' use a different verb style, but overall the naming is largely predictable.

Tool Count2/5

With 67 tools, the count is excessive for a vacation rental server, leading to bloat and potential overwhelm. Many tools could be consolidated (e.g., multiple risk analysis tools, duplicate property detail fetchers), and the scope feels unfocused, including niche tools like those for Philadelphia events or World Cup compliance that might be better handled as parameters in broader tools.

Completeness5/5

The tool set provides comprehensive coverage for the vacation rental domain, including booking, risk assessment, compliance, maintenance, evidence management, and guest interactions. There are no obvious gaps; it supports full CRUD/lifecycle operations and specialized workflows, ensuring agents can handle most scenarios without dead ends.

Resources