Skip to main content
Glama

jobd_submit

Submit shell commands as jobs to a distributed broker. Queue and route tasks across GPU-capable workers with support for synchronous waiting, job arrays, and parameter sweeps.

Instructions

Submit a job to the jobd broker. Default async; pass wait=true to block up to wait_timeout_s (server clamps to 270).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
commandYesShell command run by the worker shell.
projectYesPriority lookup key; falls back to _default.
cwdYesAbsolute path; broker validates against worker mount_roots.
needsNoTool tags (R, python3, cuda).
gpuNoPin to GPU-capable worker.
hostNoHost alias pin (laptop, desktop-vm).
waitNoSync mode: block until terminal or timeout. For an array submit (count/sweep), waits on every member under one shared deadline and returns an aggregate {array_id, count, job_ids, states, all_completed, members:[{job_id, state, exit_code}]}.
wait_timeout_sNoSeconds; permissive — server clamps to 270.
dry_runNoPreview mode: run full validation + routing decision (profile, project defaults, cwd, depends_on, preflight, gpu_contention) and return the would-be plan WITHOUT queueing. Response has state='dry-run', would_route_to (list[host]), would_use_worker (host or null), validation (resolved fields + warnings). Per dry-run convention 2026-05-18.
extraNoEscape hatch: idempotent (bool), depends_on (int[]), depends_on_any_exit (bool), priority (int delta), max_wall_s (int), idle_timeout_s (int), checkpoint_grace_s (int 1..300), vram_gb (float — explicit GPU VRAM the job needs at dispatch; falls back to cuda-Ngb tier-tag max, then to 2 GB floor for --gpu jobs), count (int 1..1000 — submit a job array of N members, with `{i}` in the command replaced by the 0-based index; response is {array_id, count, job_ids, warnings} instead of a single job), sweep (list of {key, values[]} — parameter-sweep axes; broker fans out the cartesian product, substituting `{key}` per member plus `{i}`; mutually exclusive with count; product capped at 1000), profile (str), env (dict), preemptible (bool).
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses async/sync modes, timeouts, and the dry_run preview behavior. It does not mention error handling or side effects, but the core behaviors are sufficiently covered.

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

Conciseness5/5

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

Two sentences with zero waste. The purpose is front-loaded, and the optional sync behavior is stated efficiently. Every word earns its place.

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

Completeness2/5

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

No output schema is provided, and the description does not explain return values (e.g., job ID or status). For a complex tool with 10 parameters, the description lacks critical information about what the function returns, making it incomplete.

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 description coverage is 100%, so baseline is 3. The tool description adds minimal extra meaning beyond the schema, only reiterating wait behavior and default. It does not provide significant additional context for other parameters.

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 clearly states 'Submit a job to the jobd broker' with a specific verb and resource, distinguishing it from sibling tools like jobd_cancel (cancel) and jobd_list (list).

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

Usage Guidelines4/5

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

The description explains the default async behavior and when to use sync mode via 'wait=true', including a timeout constraint. It does not explicitly state when not to use or mention sibling alternatives, but the guidance is clear for the primary choice.

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/musharna/jobd'

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