Skip to main content
Glama

submit_job

Queue a 3D print job by specifying the G-code file, optional printer, and priority. Use an idempotency key to retry failed submissions without creating duplicate prints.

Instructions

Submit a print job to the queue.

Free tier allows up to 10 queued jobs for single-printer use.
Pro tier unlocks unlimited queue depth with multi-printer scheduling.

Args:
    file_name: G-code file name (must already exist on the printer).
    printer_name: Target printer name, or omit to let the scheduler
        pick any idle printer.
    priority: Higher values are scheduled first (default 0).
    idempotency_key: Optional opaque key (e.g. a UUID you generate)
        naming this one submission.  If your call fails in a way
        where you cannot tell whether the job was queued — a timeout,
        a dropped connection — retry with the SAME key: you will get
        the original job back (``submission: "replayed"``) instead of
        queuing a duplicate print.  Use a NEW key for each job you
        genuinely want printed; reusing a key with different
        parameters is refused.

Jobs are executed in priority order, with FIFO tie-breaking.
Use ``job_status`` to check progress and ``queue_summary`` for an overview.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
priorityNo
file_nameYes
printer_nameNo
idempotency_keyNo
Install Server

TDQS

A4.7/5.0
Behavior5/5

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

No annotations are provided, so the description carries full behavioral disclosure. It covers queue depth limits, scheduling behavior, priority ordering with FIFO tie-breaking, idempotency semantics including replay responses and rejection on key misuse, and the requirement that the file must already exist.

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?

The description is well structured: use-case summary first, then tier constraints, per-argument semantics, scheduling order, and related tools. Every sentence adds useful information without unnecessary filler, and the idempotency explanation is detailed but necessary.

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 no output schema and no annotations, the description compensates well by explaining job queue behavior, ordering, retry semantics, and follow-up tooling. However, it never describes what a normal successful submission returns (e.g., whether a job ID is issued), so an agent may lack some clarity about the direct response shape.

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

Parameters5/5

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

Schema description coverage is 0%, but the description gives detailed meaning to each of the four parameters: file_name prerequisite, printer_name selection behavior, priority ordering semantics, and the crucial idempotency_key retry/replay contract.

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 opens with a direct verb-object statement: "Submit a print job to the queue." It specifies the resource (print job queue), the action (submit), and clearly separates this submission tool from follow-up tools like job_status and queue_summary.

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 gives concrete context about tier limits, single vs multi-printer scheduling, retry behavior, and points the agent to job_status for progress and queue_summary for overview. It does not explicitly exclude alternative submission tools like fleet_submit_job or route_print_job, but it describes the queued-job context well enough for most selection decisions.

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

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/codeofaxel/kiln'

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