Skip to main content
Glama

recommend_material

Read-only

Translates print intent and printer capabilities into a material recommendation with settings, considering enclosure, heated bed, budget, and on-hand inventory constraints.

Instructions

Recommend material from intent + printer capabilities (considers enclosure, bed, budget).

        Uses printer DNA + historical data to translate natural language
        intent (e.g. ``"make it strong"``, ``"make it pretty"``,
        ``"make it cheap"``) into an optimal material recommendation
        with settings.

        Pass ``printer_id`` to answer for a SPECIFIC machine — essential
        on a mixed fleet, where "what should I run this in" depends on
        which printer will run it.  The recommendation is then computed
        against that machine's nozzle state (abrasive materials on a
        brass nozzle get an explicit wear warning) and the response
        names the machine it answered for.

        Pass ``on_hand_only=True`` to recommend only from materials you
        physically have — recorded spools (``add_spool``) plus what's
        loaded on your machines (AMS/CFS sync).  Scoped to one printer
        this works on every tier; sweeping a multi-machine fleet in one
        call is a Kiln Business feature.  The recommendation's
        ``availability`` block then says WHERE the material is: which
        machine has it loaded, or that it's on the shelf and needs a
        spool swap first.  With ``printer_id`` the loaded half is
        scoped to that one machine (shelf spools always count — they
        can be swapped in); without it, every machine's load counts.
        When nothing on hand suits the request, the response returns
        the best catalog pick clearly labeled needs-purchase — it
        never silently widens to the catalog.  And when what you have
        works but a material you DON'T own fits the job materially
        better, the answer names that too, so "best of what you have"
        is never mistaken for "right for the job".

        **Which material tool to use:**

        - Quick intent-based pick for your own printer? → ``recommend_material`` (this tool)
        - Only from spools I actually own? → ``recommend_material(on_hand_only=True)``
        - Designing a part and need engineering specs? → ``recommend_design_material``
        - Ordering a print from a service? → ``suggest_material_for_order``
        - Which of MY printers has a material loaded? → ``find_printers_with_material``
        - What's loaded across the fleet right now? → ``get_fleet_material_summary``

        Args:
            intent: User intent text (e.g. ``"strong"``, ``"pretty"``).
            has_enclosure: Whether the printer has an enclosure.
            has_heated_bed: Whether the printer has a heated bed.
            budget_usd: Optional maximum budget per kg in USD.
            printer_id: Optional registered printer to answer for.
                Empty = printer-agnostic recommendation.
            on_hand_only: Restrict candidates to recorded inventory
                (loaded materials + shelf spools).  Default False =
                full catalog.
        

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": {
      "intent": "<intent>"
    },
    "name": "recommend_material"
  }
}

Input Schema

NameRequiredDescriptionDefault
intentYesUser intent text (e.g. ``"strong"``, ``"pretty"``).
budget_usdNoOptional maximum budget per kg in USD.
printer_idNoOptional registered printer to answer for. Empty = printer-agnostic recommendation. Default: "".
on_hand_onlyNoRestrict candidates to recorded inventory (loaded materials + shelf spools). Default False = full catalog. Default: false.
has_enclosureNoWhether the printer has an enclosure. Default: false.
has_heated_bedNoWhether the printer has a heated bed. Default: true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.5.1
    • addedInput schema / properties / budget_usd / description
      Added value: +"Optional maximum budget per kg in USD."
    • changedInput schema / properties / has_enclosure / description
      Previous value: -"Default: false."New value: +"Whether the printer has an enclosure. Default: false."
    • changedInput schema / properties / has_heated_bed / description
      Previous value: -"Default: true."New value: +"Whether the printer has a heated bed. Default: true."
    • addedInput schema / properties / intent / description
      Added value: +"User intent text (e.g. ``\"strong\"``, ``\"pretty\"``)."
    • changedInput schema / properties / on_hand_only / description
      Previous value: -"Default: false."New value: +"Restrict candidates to recorded inventory (loaded materials + shelf spools).  Default False = full catalog. Default: false."
    • changedInput schema / properties / printer_id / description
      Previous value: -"Default: \"\"."New value: +"Optional registered printer to answer for. Empty = printer-agnostic recommendation. Default: \"\"."
  2. Changed9 schema fields changedv1.5.0
    • removedInput schema / properties / budget_usd / default
      Removed value: -null
    • removedInput schema / properties / has_enclosure / default
      Removed value: -false
    • addedInput schema / properties / has_enclosure / description
      Added value: +"Default: false."
    • removedInput schema / properties / has_heated_bed / default
      Removed value: -true
    • addedInput schema / properties / has_heated_bed / description
      Added value: +"Default: true."
    • removedInput schema / properties / on_hand_only / default
      Removed value: -false
    • addedInput schema / properties / on_hand_only / description
      Added value: +"Default: false."
    • removedInput schema / properties / printer_id / default
      Removed value: -""
    • addedInput schema / properties / printer_id / description
      Added value: +"Default: \"\"."
  3. Changed2 schema fields changedv1.3.0
    • addedInput schema / properties / on_hand_only
      Added value: +{
      +  "default": false,
      +  "title": "On Hand Only",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / printer_id
      Added value: +{
      +  "default": "",
      +  "title": "Printer Id",
      +  "type": "string"
      +}
  4. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint/openWorldHint/destructiveHint, and the description goes far beyond them: nozzle-wear warnings for abrasive materials on brass, an 'availability' block stating where material physically sits, an explicit promise that it never silently widens to the catalog, and needs-purchase labeling. These are non-obvious behavioral guarantees an agent could not infer from structured fields.

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?

Purpose is front-loaded and the body is organized into a scoping paragraph, an on-hand paragraph, and a routing list, making it easy to scan. The on_hand_only paragraph is dense and repeats the printer-scoping point three times, so it is thorough rather than maximally tight.

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?

There is no output schema, yet the description still explains the return shape (availability block, machine named, needs-purchase labeling) and the fallback logic when nothing on hand fits. For a read-only 6-parameter recommendation tool, nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description still adds real meaning for printer_id (recommendation computed against that machine's nozzle state, response names the machine) and on_hand_only (shelf spools always count, loaded inventory is scoped by printer_id). budget_usd, has_enclosure, and has_heated_bed are only restated, not enriched, which keeps it below a 5.

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?

First sentence states a specific verb and resource ('Recommend material from intent + printer capabilities') and immediately scopes the inputs considered (enclosure, bed, budget). The dedicated 'Which material tool to use' block explicitly separates it from recommend_design_material, suggest_material_for_order, find_printers_with_material, and get_fleet_material_summary.

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?

Provides explicit routing rules as a bulleted decision list, each naming a sibling and the condition that selects it (e.g. 'Only from spools I actually own? → recommend_material(on_hand_only=True)'). It also states a when-not constraint: fleet-wide on-hand sweeps require Kiln Business, while single-printer scoping works on every tier.

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