run_command
Run non-interactive shell commands on the Amadeus login node for light tasks like checks and module setup, while enforcing approvals and routing compute work to job tools.
Instructions
Run a shell command on the login node (bash, non-interactive). $DATA, $SCRATCH, $USER expand there.
Light work only: no compute, builds or big downloads (use a job). lmod=True initialises Lmod first (for module).
Refused: Slurm-changing commands (use submit_job, cancel_job, update_job; sacctmgr only in its read-only
show/list forms, e.g. sacctmgr -nP show qos format=Name,MaxWall), ssh to compute nodes and srun (use node_exec)
and changes to SSH/shell/VPN config.
Deleting or moving files (rm, mv, rsync --delete, ...) needs the human's approval in approval, in their words.
The command is not repeated after an SSH failure; when recovery says the tunnel was restarted after a stall
(nothing ran remotely), run it again.
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": {
"command": "<command>"
},
"name": "run_command"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| lmod | No | ||
| command | Yes | ||
| approval | No | ||
| timeout_s | No |