Skip to main content
Glama
Sign In

Snapstay

by ai.snapstay
OverviewDiscussionsAdmin

Get reserved and blocked date ranges for a room

units.occupancy
Read-onlyIdempotent

Get reserved and blocked date ranges for a room. Get id from units.list or units.get. Start is included and end is excluded. End must be after start. Returns active allocations that overlap the requested dates. Returned ranges can extend beyond those dates. Use bookings.list for guest and booking details.

Input Schema

NameRequiredDescriptionDefault
idYesRoom record ID from units.list or units.get.
endYesEnd hotel date in YYYY-MM-DD format. Must be after start. This date is excluded from the requested nights.
startYesFirst hotel date to check, in YYYY-MM-DD format. End must be after start.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "end": "2026-11-03",
+    "id": "room-id-from-units-list",
+    "start": "2026-11-01"
+  }
+]
    • changedInput schema / properties / end / description
      Previous value: -"End hotel date in YYYY-MM-DD format."New value: +"End hotel date in YYYY-MM-DD format. Must be after start. This date is excluded from the requested nights."
    • changedInput schema / properties / id / description
      Previous value: -"ID of the record to get or change."New value: +"Room record ID from units.list or units.get."
    • changedInput schema / properties / start / description
      Previous value: -"Start hotel date in YYYY-MM-DD format."New value: +"First hotel date to check, in YYYY-MM-DD format. End must be after start."
  2. Changed3 schema fields changed
    • addedInput schema / properties / end / description
      Added value: +"End hotel date in YYYY-MM-DD format."
    • addedInput schema / properties / id / description
      Added value: +"ID of the record to get or change."
    • addedInput schema / properties / start / description
      Added value: +"Start hotel date in YYYY-MM-DD format."
  3. First observed

TDQS

A4.5/5.0
Behavior4/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 useful behavioral context about date inclusion/exclusion, overlapping active allocations, and returned ranges possibly extending beyond the requested window; it does not need to explain return values because an output schema exists.

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 short and front-loaded with the purpose, followed by id source, date semantics, overlap behavior, and the sibling alternative. Every sentence contributes useful selection or invocation context.

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?

Given the output schema, full annotation coverage, and complete input schema, the description supplies the remaining decision-critical context: which sibling to use, how to obtain the id, and how the date range and overlapping ranges behave.

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 schema already documents id, start, and end, including the YYYY-MM-DD format and end-after-start requirement. The description reinforces start-inclusive and end-exclusive semantics but does not add substantial parameter meaning beyond the structured schema, so the baseline 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: getting reserved and blocked date ranges for a room. It is clearly distinguishable from booking-detail and unit-listing siblings, especially by pointing to bookings.list for guest and booking details.

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

Usage Guidelines5/5

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

It explicitly tells the agent where to get the required id from units.list or units.get, and it names bookings.list as the alternative when guest and booking details are needed. The routing between occupancy lookup and booking detail lookup is clear.

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

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