Skip to main content
Glama

Guest2Host

Check dates

check_dates
Read-onlyIdempotent

Whether one stay is open for a check-in/check-out window, from the owner's own calendars (synced about every 30 minutes). When the dates are taken, returns up to three nearby open windows of the same length. If the owner has not connected a calendar, available is null: the dates are unknown, not open — send the traveler to the owner's site.

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": {
      "slug": "<slug>",
      "checkIn": "<checkIn>",
      "checkOut": "<checkOut>"
    },
    "name": "check_dates"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe stay's slug, from search_stays
checkInYesCheck-in date, YYYY-MM-DD
checkOutYesCheck-out date, YYYY-MM-DD

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 readOnly, idempotent, non-destructive behavior, and the description adds substantial context beyond that: the data source, a ~30-minute sync staleness window, a fallback that returns up to three nearby open windows when dates are taken, and the critical null semantics meaning unknown rather than open. These are exactly the details an agent needs to interpret results correctly.

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 tight sentences with no filler: purpose first, return behavior second, and the null/unknown edge case last. Each sentence carries distinct, actionable information.

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, the description takes on the burden of explaining returns and does so: a boolean/availability result, up to three alternative windows, and a null case with explicit interpretation guidance. Nothing an agent needs to call and interpret this tool is missing.

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 formats and patterns already documenting slug, checkIn, and checkOut, so the baseline is 3. The description reinforces the paired-window semantics but adds no format, constraint, or interpretation detail beyond what the schema already supplies.

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 opens with a specific verb-and-resource pair: it checks whether a single stay is open for a given check-in/check-out window, sourced from the owner's calendars. The singular 'one stay' paired with the slug parameter clearly separates it from list-style siblings like search_stays or list_destinations.

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 operational context (an owner's own synced calendars) and a concrete fallback instruction when the data is unavailable: send the traveler to the owner's site. It stops short of naming an alternative tool or stating explicit exclusions, so it is clear guidance rather than full when/when-not routing.

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.

Resources