Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

get_auto_tuned_settings

Read-only

Retrieve auto-tuned print settings from historical success/failure analysis for a specific printer and material to reduce print failures; requires Kiln Pro.

Instructions

Get auto-tuned print settings from historical success/failure analysis.

Needs Kiln Pro.

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": {
      "printer_id": "<printer_id>",
      "material": "<material>"
    },
    "name": "get_auto_tuned_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
materialYesFilament material (e.g. "PLA", "PETG", "ABS").
printer_idYesThe printer identifier.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.1
    • addedInput schema / properties / material / description
      Added value: +"Filament material (e.g. \"PLA\", \"PETG\", \"ABS\")."
    • addedInput schema / properties / printer_id / description
      Added value: +"The printer identifier."
  2. Addedv1.5.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the bar is lower. The description adds two traits not in the annotations: the settings are derived empirically from past successes and failures, and the tool requires a Kiln Pro entitlement, which predicts an authorization-shaped failure mode. It stops short of saying what happens when history is sparse or what the settings bundle 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.

Conciseness5/5

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

Two short lines with zero filler, purpose front-loaded and the entitlement caveat placed after it. Nothing could be removed without losing information.

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 two-parameter read-only tool with a fully documented schema and clear annotations, the description covers purpose, data provenance, and the plan requirement. It leaves two things an agent would want: how this differs from the other settings-recommendation siblings, and what is returned when historical evidence is thin.

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% with only two required parameters (printer_id, material), both documented with examples in the schema. The description adds no meaning about how material strings are matched or whether printer_id must be a registered printer, so the 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?

States a specific verb and resource (get auto-tuned print settings) plus the data source (historical success/failure analysis), which is more than a restatement of the name. It does not, however, distinguish itself from the many sibling settings tools in this server (get_optimal_settings, recommend_settings, predict_print_settings, infer_print_settings), so an agent must guess which one to pick.

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?

"Needs Kiln Pro" is a genuinely useful gating precondition that tells the agent when the call will fail, which is a form of usage guidance. Beyond that there is no when-to-use or when-not-to-use guidance and no mention of the closest alternatives, so selection between this and get_optimal_settings is left to inference.

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