Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

optimize_fleet_assignment

Read-only

Assign 3D print jobs to printers based on material availability, preferring color matches and fewer spool swaps across your printer fleet.

Instructions

Assign print jobs to printers by material availability.

        Each job dict should contain ``file_name``, ``material_type``,
        ``required_grams``, and optionally ``color``.  On one machine it
        says which jobs its loaded spool can take, in order; across
        several machines it picks a printer for each job, preferring
        colour matches and fewer spool swaps (Kiln Business).

        Args:
            jobs: List of job dicts, each with ``file_name``,
                ``material_type``, ``required_grams`` and optionally
                ``color``.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "jobs": "<jobs>"
    },
    "name": "optimize_fleet_assignment"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobsYesList of job dicts, each with ``file_name``, ``material_type``, ``required_grams`` and optionally ``color``.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / jobs / description
      Added value: +"List of job dicts, each with ``file_name``, ``material_type``, ``required_grams`` and optionally ``color``."
  2. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, and the description is consistent with that planning-only profile. It adds real value beyond the annotations: single-machine output is an ordered takeable-jobs list, multi-machine behavior picks a printer per job with stated preferences (colour match, fewer spool swaps), and it flags a 'Kiln Business' tier requirement. It stops short of saying what happens when material is insufficient or precisely what the return payload looks like.

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

Conciseness3/5

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

The opening line is well front-loaded, but the job-dict field list is stated twice — once in the prose and again verbatim in the Args block — which is pure repetition. The multi-machine preference clause earns its place; the duplicate field enumeration does not.

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?

For a single-parameter planning tool with no output schema, the description covers scope and assignment heuristics reasonably well. However, with no output schema it should describe the shape of the returned assignment (job-to-printer mapping, ordering, or failure reporting) and what happens when no printer can satisfy a job, which it does not.

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%, and the description's parameter guidance largely duplicates the schema's own wording for the jobs field. It does reinforce that file_name, material_type and required_grams are required while color is optional, but that meaning is already available in the schema, so the high-coverage baseline of 3 applies.

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

Purpose4/5

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

The first sentence states a specific verb and resource plus the governing constraint: 'Assign print jobs to printers by material availability.' That is enough for an agent to distinguish it from related siblings such as route_print_job or fleet_submit_job, but the description never names those alternatives, so the differentiation is inferred rather than stated.

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?

Usage is implied by the purpose sentence and clarified by the single-machine versus multi-machine distinctions, which tell an agent what the scope of each call looks like. There is no explicit when-to-use/when-not guidance and no pointer to the sibling tools that also route or submit jobs, so the agent must infer that this is a planning-only tool.

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

Deploy Server

Other Tools