Plan a task against the rack
route_taskCreates a routing plan for a natural-language task by listing candidate MCP servers from the current rack. Use it after rack_add to preview where the task could run, without executing tools.
Instructions
Produce a routing plan for a natural-language task against the current rack. In this release the planner is a deterministic stub: it lists candidate servers and does not execute downstream tools. Use after rack_add. Not a substitute for status. Read-only with respect to the rack; no network calls yet.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"task": "<task>"
},
"name": "route_task"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| task | Yes | Natural-language goal to route across racked MCP servers. | |
| preferred_server | No | Optional rack name to prefer. Empty means first match / all. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||