Skip to main content
Glama

Villa or holiday home details

al_stay_detail
Read-onlyIdempotent

Retrieve full details for a villa or holiday home by ID, including capacity, beds, amenities, rules, cancellation terms, daily prices, availability calendar, and recent reviews.

Instructions

Show one villa or holiday home in full: capacity, beds, amenities, house rules, cancellation terms, calendar, reviews.

Toman per night (price_base weekday, price_weekend, price_holiday); calendar gives availability and price per day.

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": {
      "id": "<id>"
    },
    "name": "al_stay_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes`id` from al_stays.
reviewsNoRecent reviews to include.
calendar_daysNoCalendar days to list from today.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.0
    • changedInput schema / properties / calendar_days / description
      Previous value: -"How many days of availability and nightly prices to list from today."New value: +"Calendar days to list from today."
    • changedInput schema / properties / id / description
      Previous value: -"The `id` of a place from al_stays."New value: +"`id` from al_stays."
    • changedInput schema / properties / reviews / description
      Previous value: -"How many recent guest reviews to include (0 for none)."New value: +"Recent reviews to include."
  2. First observedv0.1.2

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior, so the bar is lower. The description adds genuine context beyond that: the currency and unit of prices (Toman per night), which fields carry weekday/weekend/holiday rates, and that the calendar conveys both availability and per-day price. It does not mention error behavior for an unknown id, but the data-shape disclosure is solid.

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 content list is front-loaded in a single efficient sentence, and the price/calendar note is a compact second block. The parenthetical price explanation is slightly dense but every clause carries information; no filler.

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?

With no output schema and a mutation-free read tool, the description carries the burden of saying what comes back, and it does so by naming the returned sections and price semantics. Minor gap: it does not describe the reviews payload shape or failure mode for a bad id, but overall an agent knows what to expect.

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 all three parameters (id, reviews, calendar_days) are already documented with defaults and bounds. The description clarifies what the calendar and price fields mean in the returned data but adds nothing new about the parameters themselves; baseline 3 applies.

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 states a specific verb and resource ('Show one villa or holiday home in full') and enumerates the content returned (capacity, beds, amenities, house rules, cancellation terms, calendar, reviews). This clearly separates it from the plural list tool al_stays, though no sibling is named explicitly.

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

Usage Guidelines2/5

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

There is no explicit when-to-use, when-not, or alternative routing in the description; the only hint ('`id` from al_stays') lives in the schema, not the description. An agent can infer this is the detail lookup for a single stay, but that inference is never stated.

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