Check live stay price for a previously recommended hotel.
REQUIREMENT:
- update_stay_dates must already have been called
| Name | Required | Description | Default |
|---|---|---|---|
| session_id | Yes | ||
| hotel_index | No | ||
| hotel_code_or_name | No |
| 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?
With no annotations, the description carries the full burden. It mentions 'live' pricing and the prerequisite, which provides some behavioral context, but it does not disclose whether the operation is read-only, what happens if the prerequisite isn't met, or any side effects. It gives minimal but non-zero transparency.
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 and front-loaded with the main purpose, followed by the requirement. Every sentence earns its place. It loses one point because it is so brief that it omits essential parameter context, but as a concise description, it is well-structured.
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 tool has 3 parameters, a prerequisite, and no annotations, yet the description provides no guidance on how to identify the hotel or interpret the session context. While an output schema exists, the description does not leverage it or explain the hotel selection mechanism, leaving the description incomplete for effective tool invocation.
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%, and the description does not explain any parameters. The phrase 'previously recommended hotel' hints that hotel_index might refer to a position in a recommendation list, but it does not clarify the relationship between hotel_index and hotel_code_or_name or when to use each. The description fails to compensate for the lack of schema documentation.
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 clearly states the action ('Check live stay price') and the specific resource ('previously recommended hotel'), which distinguishes it from general search tools. However, it does not explicitly name alternatives like get_booking_offers, so it is clear but not fully differentiated from siblings.
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 requirement 'update_stay_dates must already have been called' provides a necessary prerequisite, but it does not explain when to prefer this tool over alternatives or give broader context on when it is appropriate. This is useful but incomplete 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.