No user-submitted related servers found.
Scored across 7 tools
Each tool has a clearly distinct role: discovery (instances, search_commands), introspection (command_schema), execution (read vs. modify), visual verification (view_image), and guidance (get_skill). The read/modify split is explicit, and search vs. schema is separated by discovery vs. detail lookup. No two tools appear to do the same thing.
All names share the archicad_ snake_case prefix, but action conventions are mixed: search_commands, view_image, and get_skill use verb_noun form, read and modify are bare verbs, and instances and command_schema are noun phrases. The pattern is still readable but not predictable as a uniform verb_noun convention.
Seven tools is well-scoped for an Archicad command bridge. Each tool covers a necessary part of the workflow: setup/discovery, schema lookup, read execution, modify execution, visual checking, and skill guidance. No tool feels redundant or missing from the count.
The surface covers the full bridge lifecycle: finding Archicad instances, discovering commands, reading schemas, executing non-mutating and mutating commands, visually verifying results, and retrieving procedural skills. There are no obvious dead ends for the stated purpose, and read/modify support batch operations.