No user-submitted related servers found.
Scored across 9 tools
Each tool targets a distinct stage of the job lifecycle (create, inspect, execute, reconcile) with fairly precise descriptions. The main risk is overlap among the read-only tools: studio_inspect_job, studio_status, studio_recovery_report, and studio_list_artifacts all involve inspection, though the descriptions do delineate durable state vs. host probing vs. recovery evidence vs. artifacts.
All tools share a clear 'studio_' prefix and snake_case, and most follow a verb_noun pattern (create_job, inspect_job, plan_environment, execute_action). A few, notably studio_status and studio_recovery_report, use noun forms rather than verbs, which is a minor deviation.
Nine tools is well within a healthy range and each maps to a distinct workflow stage: planning, job creation, execution, inspection, and recovery. No tool appears redundant or frivolous for the stated bridge purpose.
The surface covers the core lifecycle: plan, create, inspect, execute, list artifacts, reconcile, and recovery reporting. The notable gap is no cancellation or deletion of a job and no explicit update/re-configure operation, which agents may need for cleanup.