Skip to main content
Glama

Check availability

check_availability
Read-only

Whether CGC can take a pre-booked pickup at a given date and time. Transfers run 24/7 by pre-booking, including Christmas Day. Standard rates apply 6am–8:30pm AEST; pickups between 8:30pm and 6am carry an after-hours fee, shown in the quote before booking. Holiday hours over Christmas and New Year 2026–27 (Queensland time): Christmas Eve until 6pm, Christmas Day 6am–7pm, Boxing Day 6am–7pm, New Year's Eve until 6pm, New Year's Day from 7am. A holiday surcharge applies on Christmas Day, Boxing Day and Easter Sunday, shown in the quote before booking. Same-day requests should phone 0416 131 285. The booking engine's closed days and closed windows (holiday hours included) answer available:false with the closure message; some windows close only some vehicles. Travel within 12 hours needs direct contact.

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
paxNoPassenger count, 1-14
dateYesTravel date, YYYY-MM-DD (Australia/Brisbane)
timeYesPickup time, HH:MM 24h

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Beyond readOnlyHint and openWorldHint, it explains what the return value means: closed days and closed windows answer available:false with a closure message, and some windows close only for some vehicles. It also discloses timezone and fee semantics (AEST standard rates, after-hours and holiday surcharges shown in the quote) that matter for interpreting the result. The main remaining gap is whether the result is real-time against the booking engine or otherwise cached.

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?

The availability question is front-loaded and every block carries operational weight—fees, holiday windows, escalation routes, and the meaning of a closed window. The enumerated 2026–27 holiday hours are dense and push the important same-day/12-hour rules toward the end, slightly hurting scanability.

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 three-parameter, no-output-schema read tool, this is close to complete: an agent knows when to call it, when to redirect to a phone, how to read both positive and negative answers, and how holidays and after-hours pricing affect the verdict. Nothing essential to calling it correctly appears to be 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 coverage is 100%, so date, time, and pax count (1–14) are already documented, and the description adds only the timezone framing around the date/time pair. The pax parameter is never discussed in the description—notably whether passenger count can change availability for some vehicles—so it does not meaningfully exceed the schema baseline.

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?

The definition states a concrete question—whether a pre-booked pickup is possible at a given date and time—so the verb and resource are unambiguous. It distinguishes itself situationally from quoting and booking by framing the answer as an availability verdict with closure messages, though it never names the sibling tools (get_quote, request_booking) it complements.

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 explicit escalation conditions: same-day requests must phone 0416 131 285, and travel within 12 hours needs direct contact. What it lacks is any statement of the normal call sequence relative to get_quote or request_booking, so the agent must infer that availability precedes quoting and booking.

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