Skip to main content
Glama

RentalCal

by com.rentalcal
OverviewDiscussionsAdmin

Price a stay

get_quote
Read-only

The exact price of a stay: nightly rates, discounts, cleaning and other fees, taxes and total, in integer cents, plus any refundable damage deposit the host requires and whether it is held at booking. Returns a bookingUrl that opens the host's booking page with these dates and guests filled in, where the traveller completes the booking. If the stay is not allowed (dates taken, below the minimum stay, too many guests) the reason is returned instead.

Input Schema

NameRequiredDescriptionDefault
petsNoNumber of pets.
guestsYesNumber of guests, not counting pets or infants. Where the listing's infants is null, count babies here.
checkInYesArrival date, YYYY-MM-DD.
infantsNoChildren under the listing's infants.freeUnderAge. Free, and outside maxGuests. Only where the listing's infants is not null; leave out otherwise.
checkOutYesDeparture date, YYYY-MM-DD.
propertyIdYesA RentalCal property id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / guests / description
      Previous value: -"Number of guests, not counting pets."New value: +"Number of guests, not counting pets or infants. Where the listing's infants is null, count babies here."
    • addedInput schema / properties / infants
      Added value: +{
+  "description": "Children under the listing's infants.freeUnderAge. Free, and outside maxGuests. Only where the listing's infants is not null; leave out otherwise.",
+  "minimum": 0,
+  "type": "integer"
+}
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description goes further by detailing the price components, the refundable deposit and hold-at-booking behavior, the bookingUrl handoff, and the failure mode when a stay is not allowed, adding substantial context beyond 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?

Three dense sentences are front-loaded with the tool's output and purpose, then cover the bookingUrl and failure behavior without filler. Every sentence adds information an agent needs.

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?

With no output schema and minimal annotations, the description carries the burden of explaining return values, and it does so thoroughly: price breakdown, deposit handling, bookingUrl, and failure reasons. Nothing critical is missing for an agent to call it correctly.

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%, with each of the six parameters documented in the schema. The description references dates and guests and mentions 'too many guests' but adds no parameter syntax, format, or 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 names a specific action and resource: pricing a stay, returning nightly rates, fees, taxes, total, deposit, and a bookingUrl. It is clearly distinct from find_property/get_property, but it never explicitly names a sibling or states which sibling to use instead, so it falls short of the top bar for sibling differentiation.

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

Usage Guidelines3/5

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

Usage is implied by the content – get an exact price and booking link for a stay – but the description never states when to call this versus check_availability, find_property, or get_property, nor any prerequisites or exclusions. It gives no explicit routing guidance.

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

All RentalCal toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources