Travellers Group — Regional Australia Hotels

create_corporate_enquiry

Corporate-account or group-booking enquiry, routed to the Travellers Group corporate team. Requires guest consent, as with create_enquiry.

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

Input Schema

Name	Required	Description	Default
`company`	Yes
`contact`	Yes
`context_summary`	Yes
`consent_confirmed`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 14, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Adds consent requirement and routing information beyond annotations, but does not detail response, side effects, or failure modes. Annotations already mark as non-read-only, so description provides modest added context.

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?

Two concise sentences, front-loaded with purpose and key requirement. No fluff, but could be more detailed given parameter count.

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

Completeness2/5

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

Fails to cover required parameters, nested object structure, output expectations, or failure behavior. Underwhelming for a 4-param tool with no output schema.

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?

With 0% schema description coverage, description should explain required parameters. It only touches on consent_confirmed, leaving company, contact, and context_summary unexplained. This is a significant gap.

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?

The description clearly states the tool creates a corporate-account or group-booking enquiry routed to the corporate team, distinguishing it from sibling create_enquiry for regular enquiries.

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?

Implies use for corporate/group bookings, with mention of consent requirement. Does not explicitly state when not to use, but the context of sibling tools and 'corporate' qualifier provides clear guidance.

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?