DeltaRoute MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_workersC | Compact worker/model availability. include_usage adds measured worker counters (not coordinator/browser totals); optional since ISO timestamp scopes them. Historical success does not guarantee current login/quota. Full paths/config only when detail=full. |
| recommend_routeB | Suggest a provider using editable task-fit heuristics. The coordinator chooses based on actual capabilities, context, previous outcomes and explicit user requests. |
| submit_taskB | Delegate a task or manage a heavy workflow: create_workflow, run_step, checkpoint. See the DeltaRoute heavy-workflows reference. Heavy profiles allow bounded 30-minute attempts. Workflow code requires scoped paths and reviewed dependencies. Optional wait_seconds (up to 45) collects short jobs in one call. Default read-only; code jobs use isolated clean Git worktrees. Returns compact status/result and full artifact path, never echoes the prompt. Automatic bounded provider fallback; no paid API fallback. |
| get_taskB | Collect compact results and real token counters when exposed. wait_seconds up to 45 avoids repeated polling. Full prompts/research packet stay in artifacts; detail=full retrieves them only when needed. Truncated answers are labeled. |
| cancel_taskA | Cancel a queued or running delegated task and its child process. Keep job files and worktree for inspection. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
list_workers and recommend_route are related but distinguishable (availability vs routing advice). submit_task, get_task, and cancel_task form a clear task lifecycle, though submit_task also bundles heavy-workflow subcommands, slightly blurring its scope.
All tool names follow a consistent snake_case verb_noun pattern: list_workers, recommend_route, submit_task, get_task, cancel_task. The convention is predictable and easy to scan.
Five tools cleanly cover worker listing, route recommendation, and task submit/get/cancel. The count is well-scoped with no obvious bloat or missing essential standalone operations.
The core delegation lifecycle is covered: discover workers, get a route recommendation, submit, retrieve, and cancel tasks. Minor gaps include no list_tasks/status browsing and heavy workflow operations folded into submit_task rather than exposed separately.