Skip to main content
Glama

lilo Vacation Rentals

by io.github.lilo-property

search_vacation_rentals

Read-only

Search for vacation rental properties with structured filtering. Returns results optimized for AI deep research with id, title, url, snippet, pricing, and property attributes. Use this for broad property discovery. Supports filtering by city, state, bedrooms, price, and pet-friendliness.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoFilter by city name
limitNoMax results to return (default 10, max 50)
queryYesSearch query (e.g. 'beach house in Delaware', 'family rental near Philadelphia')
stateNoFilter by state name or abbreviation
max_priceNoMaximum nightly rate in USD
min_bedroomsNoMinimum number of bedrooms
pet_friendlyNoFilter for pet-friendly properties only

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is clear. The description adds valuable behavioral details about the return format (id, title, url, snippet, pricing, attributes) and the fact that results are 'optimized for AI deep research,' which goes 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.

Conciseness4/5

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

The description is efficient with four sentences, front-loading the main purpose first. The final sentence about filtering is somewhat redundant with 'structured filtering' in the first sentence, but overall it's well-structured and each sentence adds value.

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 the schema covers all parameters and annotations declare the tool read-only, the description adds essential context about output format and intended use case. It's complete for a search tool, though it doesn't mention pagination or result ordering, which are minor gaps.

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?

The input schema has 100% coverage for all 7 parameters, so the schema already documents each parameter. The description only summarizes the filters (city, state, bedrooms, price, pet-friendliness) without adding new meaning beyond the schema, so the baseline of 3 is appropriate.

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 searches for vacation rental properties with structured filtering, giving a specific verb and resource. It also says 'Use this for broad property discovery,' which helps differentiate from specialized siblings like search_vacation_rentals_by_amenities, though it doesn't name them explicitly.

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?

Provides explicit guidance with 'Use this for broad property discovery,' giving a clear positive use case. However, it doesn't mention when not to use it or name alternative tools for specialized searches, so it falls short of a 5.

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