waysway

ingest_user_message

Store raw user message into session context.

IMPORTANT:
This tool is no longer the main profile extraction path.

RECOMMENDED USE:
- store raw user text for context
- let the external model decide profile fields
- then call update_user_profile_from_model(...)

DEFAULT BEHAVIOR:
- append raw text into user_info
- do not aggressively infer profile fields

OPTIONAL:
- if use_fallback_extraction=True, run a lightweight fallback extractor

Input Schema

TableJSON Schema

Name	Required	Description	Default
`merge`	No
`message`	Yes
`session_id`	Yes
`use_fallback_extraction`	No

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.4/5.0

Behavior4/5

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

With no annotations to rely on, the description discloses key behavioral traits: it appends raw text into user_info (not overwrite) and does not aggressively infer profile fields by default. It also mentions the optional fallback extraction behavior. While it does not cover error handling or side effects of the 'merge' parameter, it provides substantial context beyond the bare schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with clear sections (IMPORTANT, RECOMMENDED USE, DEFAULT BEHAVIOR, OPTIONAL). Every sentence adds value, and the front-loaded core purpose makes it scannable. The length is appropriate for the tool's complexity.

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?

The description covers the purpose, recommended workflow, default behavior, and an optional parameter. It also references the sibling tool update_user_profile_from_model for the next step, providing valuable context. Minor gaps include lack of detail on the 'merge' parameter and potential side effects, but overall it is quite complete, especially given an output schema exists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has no descriptions for parameters, so the description must compensate. It adds meaning for 'message' (raw user text) and 'use_fallback_extraction' (lightweight fallback extractor). However, 'session_id' and especially 'merge' remain unexplained, leaving a gap in full parameter understanding.

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 clearly states the tool's function with 'Store raw user message into session context' and further specifies 'append raw text into user_info'. It explicitly distinguishes itself from siblings by stating 'This tool is no longer the main profile extraction path' and recommending update_user_profile_from_model for that purpose, making the tool's specific role clear.

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?

The description provides explicit usage guidance: it recommends when to use the tool ('store raw user text for context'), states what not to do ('do not aggressively infer profile fields'), and names the preferred alternative tool to call afterward ('then call update_user_profile_from_model(...)'). This is clear and actionable.

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?