ShipCheck

Each tool has a distinct role: qa_preview queues a run, qa_status polls its state, qa_get_report retrieves results, and qa_note closes a needs_review job. No overlap; boundaries are clear even from short descriptions.

All tools follow a consistent qa_verb_noun pattern (get_report, note, preview, status). The prefix unifies the API, and verb_noun structure is predictable across the entire set.

Four tools provide exactly the operations needed for a QA lifecycle: start, poll, retrieve, and close. This is well-scoped for a focused server—no bloat, no missing essentials.

The lifecycle covers preview → status → report → note, which handles the main QA flow. Minor gaps exist (no cancel/list jobs), but they are not critical for the core purpose and can be worked around.