Skip to main content
Glama

Check availability

check_availability
Read-only

Date/time bookability in Queensland time (AEST, no daylight saving) only — not prices (use get_quote for fares). Checks the operator's live settings for private Gold Coast / Brisbane / Byron Bay transfers (after-hours window, days off and blocked dates, optionally per vehicle). Times outside standard hours are bookable as after-hours requests (surcharge may apply); same-day should phone. Not a driver calendar: the operator confirms every booking.

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": {
      "date": "<date>",
      "time": "<time>"
    },
    "name": "check_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesYYYY-MM-DD in Queensland time (AEST, no daylight saving)
timeYesHH:MM 24h in Queensland time (AEST, no daylight saving)
vehicleNosedan | carnival | maxi | eqb | v300 (optional; checks that vehicle's days off)

Output Schema

NameRequiredDescriptionDefault
noteYes
reasonYes
statusYes
unavailable_vehiclesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / date / description
      Previous value: -"YYYY-MM-DD"New value: +"YYYY-MM-DD in Queensland time (AEST, no daylight saving)"
    • changedInput schema / properties / time / description
      Previous value: -"HH:MM 24h"New value: +"HH:MM 24h in Queensland time (AEST, no daylight saving)"
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "note": {
      +      "type": "string"
      +    },
      +    "reason": {
      +      "type": "string"
      +    },
      +    "status": {
      +      "enum": [
      +        "bookable",
      +        "after_hours_request",
      +        "not_bookable",
      +        "call_us"
      +      ],
      +      "type": "string"
      +    },
      +    "unavailable_vehicles": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "status",
      +    "reason",
      +    "note"
      +  ],
      +  "type": "object"
      +}
  3. Changed1 schema field changed
    • addedInput schema / properties / vehicle
      Added value: +{
      +  "description": "sedan | carnival | maxi | eqb | v300 (optional; checks that vehicle's days off)",
      +  "type": "string"
      +}
  4. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say this is a safe, open-world read; the description adds the material behavior: it reads the operator's live settings (after-hours window, days off, blocked dates), returns bookability rather than confirmation, and that the operator confirms every booking. That last point is essential to prevent an agent treating a positive result as a booking guarantee.

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?

Front-loaded with the geographic/timezone scope and the get_quote exclusion, which is the right ordering. It is dense — multiple em-dash parentheticals and clauses packed into three sentences — but nearly every clause carries distinct operational 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 an output schema already available, the description covers what remains: region scope, timezone convention, after-hours and same-day handling, vehicle-specific behavior, and the fact that availability is not confirmation. No gap that would cause a mis-call is left open.

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 coverage is 100%, including the timezone format and the vehicle enum listed in the property description, so the schema already carries parameter meaning. The description's 'optionally per vehicle' adds only marginal framing beyond that, hitting the baseline for fully documented schemas.

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?

Opens with a specific verb+resource+scope: 'Date/time bookability in Queensland time (AEST, no daylight saving) only', and immediately demarcates the boundary against get_quote ('not prices'). It also distinguishes itself from a driver calendar, so an agent can pick it apart from every sibling.

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?

Gives explicit routing rules: use get_quote for fares, phone for same-day, after-hours bookings become requests with possible surcharge. These are when-to-use and when-to-do-something-else conditions, not just context.

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.