Get detailed information for a hotel.
Use this after search_hotels when the user asks for more details
about a recommended option.
| Name | Required | Description | Default |
|---|---|---|---|
| session_id | Yes | ||
| hotel_code_or_name | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action ('Get detailed information') and does not mention whether it is read-only, what happens if the hotel is not found, or any prerequisites like an active session. This minimal disclosure leaves significant behavioral traits undisclosed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise, consisting of two short sentences. The purpose is front-loaded in the first sentence, and the second sentence adds usage context without any fluff or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description is adequate for a simple get tool with an output schema. It covers the primary use case ('after search_hotels for more details') and mentions the sequencing. However, it lacks explicit details about how to supply session_id and what constitutes 'detailed information,' but the output schema likely covers the return structure. It is minimally viable with clear gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate. However, it does not mention or explain the two parameters (session_id, hotel_code_or_name). While the names provide some hint, there is no guidance on how to obtain a session_id or what formats hotel_code_or_name accepts, leaving the agent with inadequate parameter semantics.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description begins with a specific verb and resource: 'Get detailed information for a hotel.' This clearly identifies the tool's purpose. It also distinguishes itself from sibling tools by stating it is used after search_hotels, which prevents confusion with similar search tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly provides when to use the tool: 'Use this after search_hotels when the user asks for more details about a recommended option.' This gives clear context and implies search_hotels as the alternative for initial searching, meeting the criteria for explicit usage guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have clear distinct purposes, though 'update_user_profile' and 'update_user_profile_from_model' serve similar functions with different input methods, which could cause confusion. Overall, the boundaries are generally clear.
All tool names follow a consistent verb_noun pattern using snake_case, such as 'search_hotels', 'update_stay_dates', and 'get_hotel_details'. No naming style mixing or irregularities.
With 20 tools covering hotels, homestays, flights, activities, restaurants, profile management, and session handling, the count is well-scoped for a travel assistant server. Each tool serves a distinct function without bloat.
The tool set covers core travel planning needs: search, details, offers, and profile management. However, it lacks a tool to actually confirm or book an offer, which is a noticeable gap for a complete booking flow.