nomadpoint

Despite 43 tools with overlapping travel concepts, the descriptions actively disambiguate the tricky pairs: stay vs accommodation (stop vs booking), and expense vs itinerary prices ('use update_flight instead'). Passport vs document vs visa are also distinguished. A few pairs (add_passport vs create_document, create_journey vs create_stay) still require careful reading, keeping it from a 5.

Nearly every tool follows a clean snake_case verb_noun pattern (create_flight, delete_stay, update_visa, list_journeys, set_budget). Special cases like search_airports, remove_journey_member, and get_visa_status still fit the convention. No mixing of camelCase or ambiguous verbs.

43 tools is heavy even accounting for the broad travel-planning domain (journeys, stays, flights, accommodations, activities, expenses, documents, visas, budgets, members, plus lookups). Many entities carry full CRUD, inflating the surface to a level that is more than most agents can navigate cleanly.

Most entities have create/read/update/delete coverage (flight, stay, accommodation, activity, expense, visa, journey), with budget, preferences, sharing, members, and reference lookups well covered. Minor gaps: passports can be added but not updated/deleted, and there are no single-item getters outside get_journey.