Scored across 9 tools
Each tool has a distinct role: discovery (pr_catalog, pr_skill), execution (pr_do, pr_batch), diagnostics (pr_verify, pr_install_connector), and state/IO (pr_get_sequence, pr_save_project, pr_export_frame). Minor overlaps exist — pr_catalog vs pr_skill both serve as documentation entry points, and pr_verify vs pr_install_connector status both probe the bridge — but the descriptions give clear guidance on which to pick.
All tools share the pr_ prefix and most follow a verb_noun pattern (get_sequence, save_project, export_frame, install_connector). pr_do, pr_batch, pr_catalog, pr_skill deviate slightly (bare verb or noun-only), but the set is still highly predictable.
Nine tools is well-scoped for a bridge server whose real operation surface lives behind pr_catalog/pr_do. Each tool earns its place: discovery, single execution, batch execution, diagnostics, readback, persistence, visual verification, connector install, and docs.
The meta-tool set covers the full lifecycle of a bridge session: verify, inspect, edit (via pr_do), batch, save, visually check, and repair the connector. Gaps are minor — there is no tool to enumerate projects or switch the active sequence, and undo exists only as a pr_do operation rather than a first-class tool.