Returns active structured memories for a verified traveler. Use this when you need durable personalization beyond the context already provided.
| Name | Required | Description | Default |
|---|---|---|---|
| travelerId | Yes | Verified traveler ID from the private traveler context. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, and non-destructive hints. The description adds context about memories being 'active' and 'durable,' and specifies the tool is for verified travelers, complementing annotations without contradiction.
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?
Two sentences cover purpose and usage guidance with no extraneous information. Every sentence adds value.
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?
Adequate for a simple retrieval tool with one parameter and comprehensive annotations. Minor gap: no explicit description of return value structure, though 'active structured memories' provides some context.
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 coverage is 100%, and the schema already documents the travelerId parameter with format and description. The description does not add parameter-level detail beyond what the schema provides, so baseline 3 is appropriate.
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 tool returns active structured memories for verified travelers, distinguishing it from sibling tool 'suggest_traveler_memory' which creates or suggests memories. It specifies the resource (memories) and scope (active, structured).
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?
Explicitly says to use this when durable personalization beyond provided context is needed. Provides clear context but does not explicitly list when not to use it or alternative tools.
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.
Multiple search tools (search_buildings, search_property_catalog, search_network_availability) and detail tools (get_building_details, get_property_details, get_stays_in_building) have overlapping boundaries, though descriptions clarify date and availability distinctions. The verification/handoff tools are more clearly separated but still numerous.
All tools follow a consistent snake_case verb_noun pattern (create_*, get_*, search_*, start_*, verify_*). There are no mixed casing conventions or vague generic verbs, making the set predictable and easy to scan.
With 22 tools, the server is on the heavy end of a typical MCP scope, though each tool has a defined purpose. Several narrow status and discovery helpers inflate the count, but the overall count is not yet extreme.
The booking lifecycle is incomplete: create_quote and create_provisional_booking exist, but there is no cancel, update, or explicit payment action, and get_reservation_status explicitly cannot change or cancel a reservation. Search and verification are well covered, but missing booking mutations will cause agent dead ends.