No user-submitted related servers found.
Scored across 48 tools
Most tools target distinct lifecycle stages, but several pairs overlap meaningfully: get_run/get_run_summary/status_run (the latter a deprecated alias explicitly kept), list_runs/list_run_summaries, read_artifact/read_scoped_artifact, and the diagnostic trio doctor/harness_health/setup_doctor. The descriptions do a good job of drawing the boundaries (e.g. queue_run says 'Distinct from steer_run'), and stop_service's name actively misleads about its behavior, but an agent can navigate it with careful reading.
The dominant pattern is snake_case verb_noun (start_run, get_run, list_runs, wait_run, cancel_run, steer_run), applied consistently across the run/session/deployment families. Minor deviations exist in noun-only names (doctor, harness_health) and a few unusual compounds (close_run_terminals, retry_run_with_fallback), but nothing chaotic.
48 tools is heavy even for a large orchestration domain covering runs, session history, file reads, deployment, setup, and diagnostics. Duplicates that earn no new capability — status_run as a deprecated alias, two artifact readers, three-plus diagnostic tools, many list/read variants — push this well past the justified surface.
The surface covers the domain comprehensively: run creation (start_run/start_review), continuation (reply_run/steer_run/queue_run), cancellation, polling/readback (wait_run/get_run/summaries), queue management, session history search and context, scoped project/artifact reads, deployment plan-to-execute, permission reconciliation, and operation idempotency records. No obvious dead ends for the stated harness-management purpose.