Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

get_material_recommendation

Read-only

Retrieve printer-specific slicer settings for a chosen 3D printing material. Returns hotend and bed temperatures, fan speed, and tuning tips matched to a specific printer model.

Instructions

Get printer-specific slicer settings for a material you have already chosen.

Use AFTER selecting a material — returns hotend/bed temps, fan speed, and
tips tuned to a specific printer model. For help choosing which material
to use, see ``recommend_material`` or ``recommend_design_material``.

Args:
    printer_id: Printer model identifier.
    material: Material name (e.g. ``"PLA"``, ``"PETG"``, ``"ABS"``,
        ``"TPU"``).

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_material_recommendation"
  }
}

Input Schema

NameRequiredDescriptionDefault
materialYesMaterial name (e.g. ``"PLA"``, ``"PETG"``, ``"ABS"``, ``"TPU"``).
printer_idYesPrinter model identifier.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.1
    • addedInput schema / properties / material / description
      Added value: +"Material name (e.g. ``\"PLA\"``, ``\"PETG\"``, ``\"ABS\"``, ``\"TPU\"``)."
    • addedInput schema / properties / printer_id / description
      Added value: +"Printer model identifier."
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already declare this is a read-only, non-destructive, non-open-world operation, so the safety profile is covered. The description adds useful behavioral context beyond annotations by specifying that results include hotend/bed temperatures, fan speed, and printer-model-specific tips.

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

Conciseness4/5

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

The description is front-loaded with the main purpose and usage constraint, then gives the return contents and alternatives. The Args section duplicates the schema, which is slightly redundant, but the overall wording is otherwise efficient.

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 simple read-only tool with two required parameters, 100% schema coverage, annotations covering safety, and no output schema, the description supplies enough context to invoke it correctly. It covers purpose, sequencing, alternatives, and expected returned settings.

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%, so both parameters are already documented in the input schema. The description repeats the same parameter meanings without adding format, validation, or lookup behavior beyond 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 uses a specific verb and resource: it returns printer-specific slicer settings for an already chosen material. It clearly distinguishes itself from material-selection tools by naming recommend_material and recommend_design_material as alternatives for choosing a material.

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 explicitly states the required sequence: use AFTER selecting a material. It also names the sibling tools to use when the user still needs help choosing a material, giving clear when-to-use and when-not-to-use guidance.

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