waysway

update_user_profile

Update session.user_profile using standard UserProfile fields only.

USE THIS WHEN:
- the caller already has structured profile fields

DO NOT PUT HERE:
- city
- checkin_date
- checkout_date
- raw numeric search constraints that belong in search_hotels

Preferred profile fields include:
- price_range
- budget_flexibility
- relationships
- travel_purpose
- hotel_style
- facilities_like
- surroundings_like

Input Schema

TableJSON Schema

Name	Required	Description	Default
`merge`	No
`session_id`	Yes
`user_profile`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedApr 27, 2026

TDQS

A4.3/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It adds context about standard vs non-standard fields and exclusions, but omits details about the 'merge' parameter's behavior (whether it merges or overwrites) and any side effects or requirements. This is a meaningful gap for a mutation tool.

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?

The description is well-structured with clear headings and bullet lists, making it scannable. While slightly verbose, each section contributes relevant information about usage, exclusions, and preferred fields. The format aids comprehension without excessive fluff.

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

Completeness4/5

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

For a profile update tool with an output schema, the description provides adequate guidance on when to use it, what fields to include/exclude, and a list of preferred fields. Missing details about merge semantics and validation behavior prevent a perfect score, but overall it is sufficiently complete for an agent to invoke it correctly.

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?

With 0% schema description coverage, the description compensates by listing preferred profile fields and explicitly prohibiting certain fields (city, dates, raw constraints). This adds semantic meaning to the user_profile object beyond its generic schema definition, though the 'merge' parameter is left unexplained.

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 states 'Update session.user_profile' with a specific verb and resource, and further clarifies 'using standard UserProfile fields only', distinguishing it from the sibling 'update_user_profile_from_model'. It also enumerates forbidden fields, making the purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit 'USE THIS WHEN' clause indicates the intended scenario (caller already has structured profile fields), and 'DO NOT PUT HERE' lists exclusions that clearly redirect to search_hotels for raw numeric constraints. This precisely guides tool selection among siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All waysway tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0

Disambiguation4/5

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.

Naming Consistency5/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Resources

Need Help?