Travellers Group — Regional Australia Hotels

check_availability

Read-only

Tier A handoff: returns a dated, pre-filled booking-engine link — LIVE availability and pricing are at that link. This tool never asserts that dates are available.

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

Input Schema

Name	Required	Description
`adults`	No
`check_in`	Yes	YYYY-MM-DD
`children`	No
`property`	Yes
`check_out`	Yes	YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 14, 2026

TDQS

B3.3/5.0

Behavior4/5

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

Beyond the readOnlyHint annotation, the description clarifies that the tool never asserts availability and returns a pre-filled link, providing essential behavioral context.

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 extremely concise with two sentences, front-loading the key information without any wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the main function but omits details like the exact return format and any required authorization or rate limits, leaving some ambiguity.

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

Parameters2/5

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

The description does not explain any parameters. With only 40% schema coverage, the agent is left uncertain about the meaning of 'property', 'adults', and 'children'.

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 description clearly states it returns a booking-engine link, not direct availability, which distinguishes it from tools like get_indicative_rates. However, it does not explicitly contrast with all sibling tools.

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

Usage Guidelines2/5

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

The description lacks explicit guidance on when to use this tool versus alternatives like get_indicative_rates. The term 'Tier A handoff' is ambiguous, and there is no mention of when not to use it.

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

All Travellers Group — Regional Australia Hotels tools Inspect

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

Need Help?