ryu-toolslisted

# Driving Ryu through the ryu_* tools This plugin bundles an MCP bridge to one Ryu Core node. Every tool below is namespaced `ryu_` and maps to a typed Core API call. `tools/list` reflects the live set - trust it for exact names and argument shapes over this summary. All tools are read-only except `ryu_set_active_model`, `ryu_install_skill`, and a normal `ryu_run_workflow` call. Pass `dryRun: true` to `ryu_run_workflow` for a transient read-only preview that creates no run history and skips effectful nodes. ## Health and system - `ryu_health` - is the node alive. Call this first when anything fails. - `ryu_system_status` - active engine, engine running state, sidecars, gateway reachability, mesh. - `ryu_system_info` - hardware snapshot: CPU, RAM, disk, GPU/VRAM, OS. ## Models and engines - `ryu_search_models` `{ query, limit? }` - search the catalog (Hugging Face GGUF by default). - `ryu_get_active_model` - what the local chat stack is serving now. - `ryu_set_active_model` `{ modelId, engine? }` - switch the served model. It must already be installed; the engine is usually derived from the model format. - `ryu_list_engines` - inference engines and their installed models. ## Agents and teams - `ryu_list_agents` - agents configured on the node. - `ryu_list_teams` - multi-agent teams. `agentId` values from `ryu_list_agents` are what `ryu_call_mcp_tool` needs, because Core ties each MCP tool allowlist to a registered agent. ## Skills - `ryu_list_skills` - installed skil