get_corporate_account_info
Read-only
The Travellers Group corporate-account answer as data: one account, five properties, direct billing and consolidated invoicing.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Travellers Group — Regional Australia Hotels
TDQS
B3/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true. The description adds context about returned data (one account, five properties, direct billing, consolidated invoicing), but does not disclose behavior like response format, consistency guarantees, or potential limitations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness3/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence but somewhat cryptic and not fully front-loaded. Could be more direct and concise.
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?
Given zero parameters and no output schema, the description should clearly state the tool's purpose and return value. It mentions some features but is vague about what exactly is returned.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters exist, so schema coverage is 100%. The description does not need to add parameter details. Baseline 4 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose3/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description mentions 'corporate-account answer as data' and lists features, but does not clearly state the action (e.g., 'Retrieve corporate account information'). It is distinguishable from siblings like 'get_property' by focusing on corporate accounts.
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?
No guidance on when to use this tool versus alternatives such as 'get_property' or 'search_content'. There is no mention of prerequisites or filtering 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.
TDQS
A3.7/5.0
Disambiguation5/5
Each tool has a clearly distinct purpose: availability returns a pre-filled link, enquiries are separated by type, corporate info is separate from general property info, distances vs events vs rates vs room types vs town guide vs search vs recommendation. The only potential confusion is between create_enquiry and create_corporate_enquiry, but descriptions clarify the target audience. Overall, no ambiguity.
Naming Consistency5/5
All tool names consistently follow a verb_noun pattern in snake_case (e.g., check_availability, get_distances, create_enquiry). The verbs are appropriate (check, create, get, recommend, search) and nouns clearly indicate the resource. No mixing of styles or vague verbs.
Tool Count5/5
With 12 tools, the server is well-scoped for a hotel information and enquiry system. Each tool covers a distinct aspect of the domain without overlap or unnecessary bloat. The count is within the optimal range (3-15) for an MCP server.
Completeness4/5
The tool set covers core hotel information retrieval (property, rooms, rates, distances, events, town guide) and enquiry creation (general and corporate). However, there is no tool to complete a booking or confirm availability beyond a link. This is a minor gap; agents must hand off to the booking engine. Overall, the surface is mostly complete for its stated purpose.