Skip to main content
Glama

revamp

by com.revampvacations
OverviewDiscussionsAdmin

Check availability

check_availability
Read-onlyIdempotent

Check whether a stay is available for a date range, or which time slots a tour or experience has on a date. Dates are YYYY-MM-DD; for stays endDate is the check-out day. Returns available (true/false, or null with a reason when it can't be confirmed here, e.g. hotels where a room type is chosen on the page). Use get_quote for the price.

Input Schema

NameRequiredDescriptionDefault
slugYesThe listing slug.
guestsNoParty size (default 2).
endDateNoStays: check-out, YYYY-MM-DD.
startDateYesCheck-in (stays) or activity date, YYYY-MM-DD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / endDate / description
      Previous value: -"Check-out, YYYY-MM-DD (exclusive)."New value: +"Stays: check-out, YYYY-MM-DD."
    • addedInput schema / properties / guests
      Added value: +{
+  "description": "Party size (default 2).",
+  "maximum": 30,
+  "minimum": 1,
+  "type": "integer"
+}
    • changedInput schema / properties / slug / description
      Previous value: -"The stay's slug."New value: +"The listing slug."
    • changedInput schema / properties / startDate / description
      Previous value: -"Check-in, YYYY-MM-DD."New value: +"Check-in (stays) or activity date, YYYY-MM-DD."
    • changedInput schema / required
      Previous value: -[
-  "slug",
-  "startDate",
-  "endDate"
-]New value: +[
+  "slug",
+  "startDate"
+]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds useful behavioral detail by explaining that the result can be null with a reason when availability cannot be confirmed here, including the hotel room-type case.

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 availability check, then adds only the date and return-value details needed to invoke it correctly. Every sentence carries useful information, with no filler.

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?

For a four-parameter read-only tool with no output schema, the description is complete enough: it explains the two availability modes, date semantics, the shape of the result including null cases, and when to use get_quote instead. Annotations and schema cover the remaining safety and parameter details.

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 four parameters are already documented in the input schema. The description restates the YYYY-MM-DD format and endDate check-out semantics, but does not add much parameter meaning beyond what the schema already provides.

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 names a specific verb and resource: checking availability for a stay date range or for tour/experience time slots. It clearly distinguishes these two modes and routes pricing to get_quote, so an agent can tell what this tool is for without opening the schema.

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?

It gives clear usage context for stays versus tours/experiences and explicitly says to use get_quote for price rather than this tool. It does not cover every sibling alternative, but the primary when-to-use guidance is present.

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

All revamp 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