Update session stay dates.
USE THIS TOOL FOR:
- check-in date
- check-out date
- nights-based date calculation
DO NOT:
- do NOT put dates inside user_profile
- do NOT try to pass dates through start_session user_profile
| Name | Required | Description | Default |
|---|---|---|---|
| nights | No | ||
| session_id | Yes | ||
| checkin_str | Yes | ||
| checkout_str | 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?
No annotations are provided, so the description must disclose side effects. It only says 'Update session stay dates' and gives exclusions, but does not state what happens to existing dates, whether checkout is derived from nights, or any validation or prerequisite behavior. This is insufficient for a mutating tool.
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 short, front-loaded, and uses clear headings for use cases and exclusions. Every line contributes useful information with no 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?
With no annotations, the description should cover important behavioral context. It covers purpose and selection well, but omits edge cases like what happens if both checkout and nights are provided, required session validity, or input validation rules. The output schema exists, so return values are covered elsewhere.
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?
With 0% schema coverage, the description partially compensates by mapping 'check-in date', 'check-out date', and 'nights-based date calculation' to the relevant parameters. However, it does not explain date formats, optionality beyond schema defaults, or behavior when multiple date-related parameters conflict.
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 'Update session stay dates' with a specific verb and resource. The 'USE THIS TOOL FOR' list and explicit 'DO NOT' exclusions distinguish it from siblings like update_user_profile and start_session.
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 'USE THIS TOOL FOR' and 'DO NOT' sections explicitly tell the agent when to use this tool and when not to, naming alternative targets (user_profile, start_session). This provides strong selection 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.