Kiln

Overview Schema Source Related Servers Discussions Admin

fleet_submit_job

Read-only

Redirects legacy fleet print requests without queuing anything; use plan_multi_copy_split for multi-printer jobs or submit_job for a single named printer.

Instructions

Retired: sending prints across the fleet is plan_multi_copy_split.

        One copy or many, ``plan_multi_copy_split`` reads every printer's
        plate, plans which printers take the part and where, and queues it
        on the person's go, the printers running side by side.  For one
        print on one named printer, ``submit_job`` with ``printer_name``.
        This name queues nothing any more: it only points there, so an old
        guide or habit still leads somewhere.  It reads no printer.
        :param file_path: Ignored: this name queues nothing.  Use
            ``plan_multi_copy_split`` or ``submit_job``.
        :param printer_name: Ignored: this name queues nothing.
        :param material: Ignored: this name queues nothing.
        :param priority: Ignored: this name queues nothing.
        :param idempotency_key: Ignored: this name queues nothing.
        :param preview_token: Ignored: this name queues nothing.

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": {
      "file_path": "<file_path>"
    },
    "name": "fleet_submit_job"
  }
}

Input Schema

Name	Required	Description
`material`	No	Ignored: this name queues nothing.
`priority`	No	Ignored: this name queues nothing.
`file_path`	Yes	Ignored: this name queues nothing. Use ``plan_multi_copy_split`` or ``submit_job``.
`printer_name`	No	Ignored: this name queues nothing.
`preview_token`	No	Ignored: this name queues nothing.
`idempotency_key`	No	Ignored: this name queues nothing.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv1.5.1Nov 5, 2026
- addedInput schema / properties / file_path / description
```
Added value: +"Ignored: this name queues nothing.  Use ``plan_multi_copy_split`` or ``submit_job``."
```
- addedInput schema / properties / idempotency_key / description
```
Added value: +"Ignored: this name queues nothing."
```
- addedInput schema / properties / material / description
```
Added value: +"Ignored: this name queues nothing."
```
- addedInput schema / properties / preview_token / description
```
Added value: +"Ignored: this name queues nothing."
```
- addedInput schema / properties / printer_name / description
```
Added value: +"Ignored: this name queues nothing."
```
- addedInput schema / properties / priority / description
```
Added value: +"Ignored: this name queues nothing."
```
Changed5 schema fields changedv1.5.0Oct 23, 2026
- removedInput schema / properties / idempotency_key / default
```
Removed value: -null
```
- removedInput schema / properties / material / default
```
Removed value: -null
```
- addedInput schema / properties / preview_token
```
Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "title": "Preview Token"
+}
```
- removedInput schema / properties / printer_name / default
```
Removed value: -null
```
- removedInput schema / properties / priority / default
```
Removed value: -null
```

Changed1 schema field changedv1.3.1Aug 19, 2026

addedInput schema / properties / idempotency_key

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Idempotency Key"
+}

First observedv0.1.0Jul 4, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the read-only annotations, the description discloses the critical behavior that this tool is a retired alias that queues nothing and reads no printer. It also states that all inputs are ignored, which is exactly the behavioral context an agent needs to avoid invoking it for real work.

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 key retirement warning is front-loaded, which is good, but the description repeats the same 'Ignored: this name queues nothing' message for every parameter. That repetition duplicates the schema and adds noise rather than useful distinction.

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

Completeness5/5

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

For a retired no-op tool, the definition covers the essential facts: it performs no action, ignores all parameters, and routes callers to the correct replacements. No output schema is needed because the tool does not produce useful output.

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 coverage is 100%, and the schema itself marks each parameter as ignored. The description reinforces that none of the parameters affect behavior, but it does not add syntax, format, or validation meaning beyond what is already in the schema.

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 immediately states that the tool is retired and that it queues nothing anymore. It clearly identifies the replacement tools for fleet/multi-copy jobs and for single named-printer jobs, so an agent can distinguish this no-op from active siblings.

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

Usage Guidelines5/5

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

It gives explicit alternatives: use `plan_multi_copy_split` for fleet planning and `submit_job` with `printer_name` for a single printer. It also explicitly says this name should not be used for actual queueing, leaving no ambiguity.

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

Deploy Server