Scored across 30 tools
Tools are mostly well separated by resource and action, with descriptions that explicitly cross-reference alternatives such as amiga_ui_click vs amiga_mouse, amiga_key_type vs amiga_key_press, and amiga_drag vs amiga_input. However, the GUI/input and ARexx families contain several adjacent tools that require careful reading to select correctly.
All tool names use a consistent amiga_ snake_case namespace and are grouped predictably by domain, e.g. amiga_ui_*, amiga_key_*, amiga_arexx_*. The only minor deviation is that many read-only discovery tools are noun phrases (amiga_info, amiga_screens, amiga_ps) while action tools are verbs, so it is not a pure verb_noun scheme.
30 tools is a heavy surface for an MCP server, and several could plausibly be consolidated, such as pointer/mouse, region_changed/screenshot, and slots/ps. The domain is genuinely broad, so most tools earn a place, but the count is above the comfortable range.
The surface covers a wide range of Amiga remote-control workflows: filesystem reads/writes, screen and UI automation, input, processes, ARexx, health, and Zenix console access. Minor gaps remain around explicit file lifecycle operations like delete, move, and mkdir, though amiga_run can usually compensate.