PutRoots

The move_task family is large but each verb suffix (answer/defer/draft) names a distinct action, and the other tools cover clearly separate resources. The only real ambiguity is move_task vs move_tasks, though the descriptions explicitly distinguish a single read-only task from a prioritized next-action feed.

All names are lowercase snake_case and the move_task_* prefix is consistent, but conventions mix imperative verbs (search_listings, start_move) with noun-style names (move_plan, listing_requirements, newcomer_options). Readable and predictable overall, with minor deviation.

11 tools is well within the ideal range for the server's scope. Each tool covers a distinct part of the newcomer/move workflow—searching, comparing requirements, offering newcomer options, starting a move, and managing tasks—without redundant helpers.

The lifecycle around listing search, requirement comparison, and task progression is well covered, with read, answer, defer, draft, and history operations. Minor gaps exist: walk and research tasks have no execution path here, and sending or submitting is deliberately left to the PutRoots web app.