Skip to main content
Glama

Check availability

get_availability
Read-onlyIdempotent

Check whether a WEE WiLDS unit is available for a date range.

Args:
    unit: One of "muckle-meadow-pod", "cosie-coorie-pod", "bb".
          The "bb" slug returns per-room availability across all 4 B&B rooms.
    check_in: Arrival date in YYYY-MM-DD format. Must not be in the past.
    check_out: Departure date in YYYY-MM-DD format. Must be after check_in.

Returns:
    For pods: {available, blocked_dates_in_range, name, url, ...}.
    For "bb": {rooms: [{room, available, ...}], any_room_available, ...}.
    On invalid input: {error, valid_units}.

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": {
      "unit": "<unit>",
      "check_in": "<check_in>",
      "check_out": "<check_out>"
    },
    "name": "get_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitYesWhich WEE WiLDS unit: "muckle-meadow-pod" (Muckle Meadow Glamping Pod), "cosie-coorie-pod" (Cosy Coorie Pod) or "bb" (the B&B, all 4 rooms).
check_inYesArrival date, YYYY-MM-DD. Must not be in the past.
check_outYesDeparture date, YYYY-MM-DD. Must be after check_in.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / check_in / description
      Added value: +"Arrival date, YYYY-MM-DD. Must not be in the past."
    • addedInput schema / properties / check_in / examples
      Added value: +[
      +  "2027-06-14"
      +]
    • addedInput schema / properties / check_out / description
      Added value: +"Departure date, YYYY-MM-DD. Must be after check_in."
    • addedInput schema / properties / check_out / examples
      Added value: +[
      +  "2027-06-17"
      +]
    • addedInput schema / properties / unit / description
      Added value: +"Which WEE WiLDS unit: \"muckle-meadow-pod\" (Muckle Meadow Glamping Pod), \"cosie-coorie-pod\" (Cosy Coorie Pod) or \"bb\" (the B&B, all 4 rooms)."
    • addedInput schema / properties / unit / enum
      Added value: +[
      +  "muckle-meadow-pod",
      +  "cosie-coorie-pod",
      +  "bb"
      +]
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), so the description's added value is in the Returns block: it discloses the pod payload shape, the per-room B&B shape with any_room_available, and the invalid-input error shape containing valid_units. That is meaningful behavioral context an agent could not get from annotations or schema. It does not discuss blocked_dates_in_range truncation or whether minimum-stay rules affect results.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The Returns block is front-loaded and earns its place, but the Args block duplicates schema descriptions that are already at 100% coverage, which is dead weight. The docstring formatting is scannable but the repeated parameter text makes the definition longer than it needs to be.

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?

There is no output schema, so the description's Returns section carries the full burden of explaining results and does so adequately for both pod and B&B paths, plus the error case. Remaining gaps (whether availability accounts for min-stay rules, how large blocked_dates_in_range can get) are minor for a three-parameter read-only lookup.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema coverage the baseline is 3, and the description modestly exceeds it by explaining that the "bb" slug changes the semantics of the result (per-room availability across all 4 rooms) rather than just enumerating values. The check_in/check_out descriptions largely restate the schema verbatim, so the gain is incremental rather than substantial.

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?

"Check whether a WEE WiLDS unit is available for a date range" states a specific verb (check availability) and resource scope (unit + date range) an agent can act on immediately. It does not mention or differentiate from nearby tools such as get_unit_details or get_pricing, so it stops short of the sibling-differentiation bar for a 5.

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 only implied: the date constraints ("must not be in the past", "must be after check_in") and the "bb" special case suggest this is the pre-booking availability lookup. There is no explicit statement of when to choose this over get_unit_details or get_pricing, and no note on what to do if the unit is unavailable beyond inspecting the return payload.

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