Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

get_print_before_edit_fleet

Read-only

Retrieve the print state from before a mid-print edit across multiple printers at once, so you can compare or recover fleet-wide changes.

Instructions

Get the print from before a mid-print edit on N printers at once (Business+).

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": {
      "sessions": "<sessions>"
    },
    "name": "get_print_before_edit_fleet"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionsYesRequired, non-empty: one dict per printer with ``printer_name`` and either ``session_id`` or ``engine_output_dir``. A session recorded for a different printer than the one it is filed under is reported as a mismatch rather than returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.1

TDQS

A3.7/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, so the safety profile is clear. The description adds useful behavior beyond that by noting the Business+ entitlement and batch scope across N printers, though it does not describe the return payload.

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?

A single front-loaded sentence with no redundant wording. The fleet scope and Business+ constraint are both stated compactly.

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 simple read-only tool with one fully documented parameter, the definition is mostly adequate. However, there is no output schema, and the description never clarifies what form 'the print' is returned in, leaving a meaningful gap for an agent invoking it.

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 schema already explains that sessions is a non-empty list of dicts with printer_name and either session_id or engine_output_dir, including mismatch handling. The description adds only the batch notion of 'N printers at once', so the schema does most of the work.

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?

States a specific verb ('Get') and resource ('the print from before a mid-print edit') with fleet scope ('N printers at once') and tier ('Business+'). It distinguishes retrieval from sibling mutation tools like add_feature_during_print_fleet or decorate_during_print_fleet, though 'the print' remains somewhat undefined jargon.

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 usage context is implied: retrieve pre-edit print state across multiple printers before a mid-print edit. The Business+ prerequisite is noted, but there are no explicit when-not conditions and no alternative sibling is named.

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