Tripmo

The set splits cleanly along read/write/lifecycle lines: list_trips → get_trip → query for reads, write for mutations, history/undo for change tracking, and dedicated tools for joining, seats, and feedback. The one genuinely confusable pair is attach_file vs upload_link, but both descriptions explicitly state which host/situation each is for, so an agent can route correctly. No two tools appear to do the same thing.

Names are uniformly snake_case and mostly verb_noun (add_seats, attach_file, create_trip, get_trip, join_trip, list_trips, send_feedback, upload_link). A handful of single-word tools (guide, history, query, undo, write) break the pattern, but they are nouns/verbs that are still immediately readable and unambiguous.

13 tools is squarely in the well-scoped range, and each earns its place: the domain is large but is compressed by consolidating all mutations into a single batch-oriented `write` and all search into `query`. There is no obvious padding or redundant surface.

Coverage is broad: trip creation, joining, reading, full record CRUD via write, undo, history, file attachment, seat purchase, and feedback, including edge cases like locked trips and ownership transfer. The gaps (deleting a trip and changing view-sharing are web-only by deliberate design) are documented rather than silent, so agents can redirect users instead of failing.