Skip to main content
Glama

Livuma — Bali rental & property search

Check availability and price

check_availability
Read-onlyIdempotent

Checks whether a listing can be booked for given dates, at which rate and for how much — the same answer the listing page gives a visitor. Returns { available, reason, recommendedRate, options, bookedRanges, bookingUrl }. Each option states whether that rate is eligible (and why not), the rate per period, the first payment and the full payment schedule. Livuma charges guests no service fee, so the amounts are what the guest pays. bookingUrl opens the listing on livuma.com with these dates selected; the booking itself (card authorisation, 3-D Secure, identity verification) is completed there by the guest.

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": {
      "listingId": "<listingId>",
      "checkInDate": "<checkInDate>"
    },
    "name": "check_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
listingIdYesThe listing's "id" from search results (GUID), a short /s/{id} id, or the listing URL.
rentalModeNo"dates" (default), "open_ended" (no end date, monthly) or "yearly" (fixed 12-month term).
checkInDateYesCheck-in date, yyyy-MM-dd. Required.
checkOutDateNoCheck-out date, yyyy-MM-dd. Omit for open_ended and yearly.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds substantial context beyond that: it names the return fields, explains rate eligibility, clarifies that amounts are guest-facing with no service fee, and states that the actual booking happens externally through bookingUrl.

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?

The description is front-loaded with the core purpose and return shape, then adds only operationally relevant details about fees and where booking occurs. There is no filler, and every sentence helps the agent interpret or act on the result.

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

Completeness5/5

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

Although there is no output schema, the description enumerates the main response fields and explains how options, payments, and bookingUrl should be interpreted. For a read-only availability-and-price check, this gives the agent enough context to call the tool and understand the result.

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 input schema already explains listingId, rentalMode, checkInDate, and checkOutDate. The description does not add parameter-level meaning beyond the schema, so the baseline score of 3 is appropriate.

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 states a specific verb and resource: checking whether a listing can be booked for given dates, including rate and total cost. It also frames the result as the same answer the listing page gives a visitor, which is concrete and distinguishes the tool from listing search or detail retrieval.

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?

The description makes the usage context clear: this is the tool for date-specific availability and pricing. It does not explicitly name alternatives such as search_listings or get_listing_details, but the intended context is sufficiently clear without exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.