Skip to main content
Glama

import_third_party_calibration

Read-only

Import OrcaSlicer, Bambu Studio, or PrusaSlicer calibration profiles to assess reliability and identify settings to fix before printing.

Instructions

Read your slicer's calibration, say how far to trust it, and what to fix.

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": {
      "tool_name": "<tool_name>"
    },
    "name": "import_third_party_calibration"
  }
}

Input Schema

NameRequiredDescriptionDefault
tool_nameYes``"orcaslicer"`` | ``"bambustudio"`` | ``"prusaslicer"``. Unknown tool names return an empty calibration_profile and an UNKNOWN tier.
config_pathNoOptional explicit path to a single config file. When omitted, walks the user-data root for ``tool_name`` and returns the first profile found. On Kiln's servers the file is required: the caller's Kiln sends it with the call (a ``.json`` profile from OrcaSlicer or Bambu Studio, a ``.ini`` from PrusaSlicer). Default: "".
printer_modelNoOptional printer-model filter (e.g. ``"bambu_a1"``). Default: "".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.5.1
    • changedInput schema / properties / config_path / description
      Previous value: -"Default: \"\"."New value: +"Optional explicit path to a single config file.  When omitted, walks the user-data root for ``tool_name`` and returns the first profile found. On Kiln's servers the file is required: the caller's Kiln sends it with the call (a ``.json`` profile from OrcaSlicer or Bambu Studio, a ``.ini`` from PrusaSlicer). Default: \"\"."
    • changedInput schema / properties / printer_model / description
      Previous value: -"Default: \"\"."New value: +"Optional printer-model filter (e.g. ``\"bambu_a1\"``). Default: \"\"."
    • addedInput schema / properties / tool_name / description
      Added value: +"``\"orcaslicer\"`` | ``\"bambustudio\"`` | ``\"prusaslicer\"``.  Unknown tool names return an empty calibration_profile and an UNKNOWN tier."
  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 declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, and the description is consistent with that read-only profile. It adds a concrete entitlement constraint with 'Needs Kiln Pro' and indicates the output includes a trust assessment and recommended fixes, though it does not detail error behavior or output structure.

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?

The description is two short sentences with no wasted wording. The purpose is front-loaded and the separate Pro requirement is easy to scan.

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 tool is a relatively simple read-only import with a fully documented input schema, but no output schema exists and the description does not clarify what the trust assessment or fixes look like. It also does not distinguish reporting recommendations from applying them, which matters given siblings like apply_calibration_recommendations.

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 detailed parameter descriptions including supported tool names and behavior for unknown tools. The description adds no parameter-level meaning beyond the schema, so the baseline score of 3 is appropriate.

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 description states a clear action and resource: read the slicer's calibration, assess trust, and identify fixes. It does not explicitly differentiate this from sibling calibration tools such as assess_calibration_status or apply_calibration_recommendations, so it stops short of a 5.

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: use this when importing/reading calibration from an external slicer. The prerequisite 'Needs Kiln Pro' is stated, but there is no explicit when-not guidance or comparison to related calibration tools, leaving the agent to infer routing.

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