No user-submitted related servers found.
Scored across 12 tools
The three job-launch tools (copilot_delegate, copilot_start, copilot_orchestrate) share a purpose, but their descriptions draw clear lines: routed default, advanced explicit-model bypass, and recursive opt-in. Similarly, steer vs. feedback vs. cancel are distinguished by timing (mid-run correction, post-run outcome recording, termination). A few boundaries still require careful reading, but an agent can select correctly.
Every tool uses the same 'copilot_' prefix plus a single snake_case token, which is highly predictable and easy to scan. The minor deviation is that some tokens are nouns (changes, jobs, models, events, feedback) while others are verbs (delegate, apply, start, steer, cancel, forget), so the verb_noun convention is not fully uniform.
Twelve tools is well within the healthy range and each maps to a distinct lifecycle stage: launch, observe, correct, terminate, review, apply, and clean up. Even the narrower utilities (copilot_models, copilot_feedback, copilot_forget) support a real need in the delegation workflow rather than padding the surface.
The surface covers the full job lifecycle, from delegation and long-poll event streaming through steering, cancellation, diff review, hash-gated apply, and memory cleanup. Gaps are minor: there is no direct single-job status/metadata fetch (relying on list plus events) and no way to discard a staged change set without applying or forgetting the job.