Skip to main content
Glama

submit_job

Submit compute jobs to SLURM clusters by defining commands, resource allocations, environment activation, and log output. Supports local or remote submission via SSH.

Instructions

Submit a SLURM job.

Args:
    command: Shell command to execute (e.g. "python train.py --epochs 100")
    name: Job name for identification in SLURM queue
    nodes: Number of compute nodes to allocate
    gpus_per_node: Number of GPUs per node (0 for CPU-only)
    ntasks_per_node: Number of tasks per node
    cpus_per_task: Number of CPUs per task
    memory_per_node: Memory per node (e.g. "32GB", "64G")
    time_limit: Wall time limit (e.g. "4:00:00", "1-00:00:00")
    partition: SLURM partition name (e.g. "gpu", "cpu")
    nodelist: Specific nodes to use (e.g. "node001,node002")
    conda: Conda environment name to activate before running
    venv: Path to Python virtual environment to activate
    env_vars: Additional environment variables as key-value pairs
    log_dir: Directory for stdout/stderr log files
    work_dir: Working directory for the job (defaults to cwd)
    transport: Cluster selector — omit / "local" for local SLURM, or an
        SSH profile name to submit to that remote cluster.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNojob
venvNo
condaNo
nodesNo
commandYes
log_dirNologs
env_varsNo
nodelistNo
work_dirNo
partitionNo
transportNo
time_limitNo
cpus_per_taskNo
gpus_per_nodeNo
memory_per_nodeNo
ntasks_per_nodeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description must disclose behavior. It omits key traits like if submission is synchronous/asynchronous, job lifecycle effects, error handling, or if it returns a job ID. The description focuses on parameters, not behavioral side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a readable parameter list preceded by a clear summary. It is not overly verbose, but is somewhat lengthy due to 16 parameters. Front-loaded with the purpose, which is good.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema (context signals), return values are covered. The description covers all 16 parameters with brief explanations, addresses local vs remote submission via 'transport', and includes defaults. Missing some context like default for work_dir, but overall sufficient for a complex tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so description must explain parameters. It adds one-line explanations (e.g., 'Shell command to execute', 'Job name for identification'), which is helpful but minimal. Some parameters like 'nodelist' just repeat the parameter name. Overall, adds some value beyond schema types.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description starts with 'Submit a SLURM job', a specific verb+resource, and the parameter list makes it distinct from sibling tools like cancel_job or get_job_logs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus siblings. It does not mention whether to use submit_job for batch jobs, interactive jobs, or alternatives like run_workflow.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ksterx/srunx'

If you have feedback or need assistance with the MCP directory API, please join our Discord server