Skip to main content
Glama
codeofaxel

Kiln

by codeofaxel
OverviewSchemaRelated ServersScoreDiscussions
Python

fleet_submit_job

Submit print jobs to the fleet orchestrator for automatic printer assignment and job tracking through completion.

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).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
materialNo
priorityNo
file_pathYes
printer_nameNo

Tool Definition Quality

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It discloses basic behavior (submit, auto-assign, track) but does not mention potential side effects, required permissions, error handling, or what happens on failure. Adequate but not rich.

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 concise with a brief intro and a structured parameter list. It is front-loaded with the purpose. Minor verbosity with the 'Args' formatting, but overall efficient.

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

Completeness3/5

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

The description lacks output semantics, such as what the tool returns (e.g., job ID). Given no output schema, this is a gap. It mentions tracking but doesn't link to status checking tools. Moderately complete for a submission tool.

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

Parameters4/5

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

Schema description coverage is 0%, so the description adds significant value. It explains each parameter's purpose, notes default behavior for printer_name, and lists possible values for priority. This compensates well for the schema's lack of descriptions.

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 print job to the fleet orchestrator,' specifying a specific verb and resource. It distinguishes from sibling tools like 'submit_job' by targeting the fleet orchestrator and mentions auto-assignment behavior.

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

Usage Guidelines3/5

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

The description provides context that auto-assignment occurs if no printer is specified, but it does not explicitly guide when to use this tool versus alternatives like 'route_print_job' or when not to use it. No exclusions or comparisons with siblings are given.

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

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