Skip to main content
Glama

fleet_submit_job

Submit a print job to the Kiln fleet orchestrator by providing a file path, with optional printer name, material, priority, and idempotency key to prevent duplicate submissions.

Instructions

Submit a print job to the fleet orchestrator.

        If no printer is specified, the orchestrator auto-assigns to the best
        available printer. Tracks the job through completion.

        Args:
            file_path: Path to the file to print.
            printer_name: Specific printer to assign to (auto-routes if None).
            material: Required filament material.
            priority: Job priority (low, normal, high).
            idempotency_key: Optional opaque key (e.g. a UUID you
                generate) naming this one submission.  If the call
                fails in a way where you cannot tell whether the job
                was queued, retry with the SAME key to get the
                original job back (``submission: "replayed"``)
                instead of queuing a duplicate print.  Use a new key
                for each job you genuinely want printed.
        

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
materialNo
priorityNo
file_pathYes
printer_nameNo
idempotency_keyNo
Install Server

TDQS

A4.4/5.0
Behavior4/5

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

It notes that the job is tracked through completion and explains the idempotency_key behavior in detail, which is valuable. However, it does not disclose side effects (e.g., resource consumption, error behaviors) beyond auto-assignment, so full transparency is not achieved.

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 well-organized with a clear overview, a note on auto-assignment, and an Args list. It is moderately verbose but each part adds value; no redundancy. It could be tightened without losing meaning, but is acceptable.

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?

It covers the core purpose, key behaviors, and parameter meanings. It lacks details on return values (though no output schema), error conditions, or post-submission workflow beyond 'tracks through completion'. This is sufficient for most use cases but not exhaustive.

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?

All five parameters are described: file_path, printer_name (auto-routes if None), material (required), priority (values listed), and idempotency_key (purpose and retry semantics). This adds meaning far beyond the schema's type-only definitions, achieving full coverage.

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 explicitly states 'Submit a print job to the fleet orchestrator' and elaborates on auto-assignment, making it distinct from simple submit tools. It clearly differentiates via 'fleet' and 'auto-assign' behavior.

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 implies when to use this tool (for fleet submission, especially when no specific printer is required) but does not explicitly compare with alternatives like 'submit_job' or 'start_print'. The auto-assign note gives context, but explicit when-to-use vs. other tools is absent.

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