Travellers Group — Regional Australia Hotels

create_enquiry

Sends a booking enquiry to the property team (groups, crews, blocks, weekly stays, functions). Requires the guest’s explicit consent to pass their details and conversation context to the property.

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>",
      "contact": "<contact>",
      "context_summary": "<context_summary>",
      "consent_confirmed": "<consent_confirmed>"
    },
    "name": "create_enquiry"
  }
}

Input Schema

Name	Required	Description
`dates`	No
`party`	No
`contact`	Yes
`property`	Yes
`context_summary`	Yes	Party, dates, purpose, questions asked — so the team replies informed
`consent_confirmed`	Yes	Must be true: the guest has consented to their details + context being sent to the property

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 14, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations indicate it's not read-only and not idempotent; description adds that it sends to the property team and requires consent, which is useful context beyond annotations.

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?

Two sentences, front-loaded with purpose and key requirement, no 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?

Covers the essential action and consent requirement, but lacks information on error handling, confirmation, or when not to use, given the tool's complexity (6 params, nested objects).

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?

Schema description coverage is low (33%) and the description only minimally elaborates on parameters beyond what's in the schema (e.g., context_summary details).

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 sends a booking enquiry and lists covered areas (groups, crews, etc.), but does not differentiate from the sibling tool 'create_corporate_enquiry'.

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?

It mentions the prerequisite of explicit consent, but gives no guidance on when to use this tool versus alternatives like 'create_corporate_enquiry'.

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?