Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

recommend_design_material

Read-only

Analyzes functional requirements and printer capabilities to recommend a suitable material for engineering parts, returning reasoning, warnings, and alternatives.

Instructions

Recommend material for engineering/functional parts (strength, heat, environment).

        Analyzes functional requirements and recommends the optimal
        material considering mechanical needs, environmental exposure,
        printer capabilities, and ease of printing.  Returns the top
        recommendation with reasoning, warnings, and alternatives.

        **Which material tool to use:**

        - Designing a part and need engineering specs? → ``recommend_design_material`` (this tool)
        - Quick intent-based pick for your own printer? → ``recommend_material``
        - Ordering a print from a service? → ``suggest_material_for_order``

        Args:
            requirements: What the object needs to do (e.g. "hold 5 kg
                of books on an outdoor shelf").
            printer_has_enclosure: Whether the printer has an enclosed
                build chamber (needed for ABS, ASA, Nylon, PC).
            printer_has_direct_drive: Whether the printer has a direct
                drive extruder (needed for TPU).
            max_hotend_temp_c: Maximum hotend temperature in Celsius.

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": {
      "requirements": "<requirements>"
    },
    "name": "recommend_design_material"
  }
}

Input Schema

NameRequiredDescriptionDefault
requirementsYesWhat the object needs to do (e.g. "hold 5 kg of books on an outdoor shelf").
max_hotend_temp_cNoMaximum hotend temperature in Celsius. Default: 300.
printer_has_enclosureNoWhether the printer has an enclosed build chamber (needed for ABS, ASA, Nylon, PC). Default: false.
printer_has_direct_driveNoWhether the printer has a direct drive extruder (needed for TPU). Default: true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.5.1
    • changedInput schema / properties / max_hotend_temp_c / description
      Previous value: -"Default: 300."New value: +"Maximum hotend temperature in Celsius. Default: 300."
    • changedInput schema / properties / printer_has_direct_drive / description
      Previous value: -"Default: true."New value: +"Whether the printer has a direct drive extruder (needed for TPU). Default: true."
    • changedInput schema / properties / printer_has_enclosure / description
      Previous value: -"Default: false."New value: +"Whether the printer has an enclosed build chamber (needed for ABS, ASA, Nylon, PC). Default: false."
    • addedInput schema / properties / requirements / description
      Added value: +"What the object needs to do (e.g. \"hold 5 kg of books on an outdoor shelf\")."
  2. Changed6 schema fields changedv1.5.0
    • removedInput schema / properties / max_hotend_temp_c / default
      Removed value: -300
    • addedInput schema / properties / max_hotend_temp_c / description
      Added value: +"Default: 300."
    • removedInput schema / properties / printer_has_direct_drive / default
      Removed value: -true
    • addedInput schema / properties / printer_has_direct_drive / description
      Added value: +"Default: true."
    • removedInput schema / properties / printer_has_enclosure / default
      Removed value: -false
    • addedInput schema / properties / printer_has_enclosure / description
      Added value: +"Default: false."
  3. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish the safe read-only profile, and the description adds genuine behavioral context: what factors are weighed (mechanical needs, environmental exposure, printer capabilities, ease of printing) and that the return includes a top recommendation plus reasoning, warnings, and alternatives. It stops short of stating determinism, failure behavior when requirements are underspecified, or whether hardware constraints can eliminate all candidates.

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?

Front-loads purpose, then routing, then parameters – a clean decision-first order. The Args section is mostly redundant with the 100%-covered schema, which costs a few lines but does not obscure anything.

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 read-only, four-parameter recommendation tool with no output schema, the description covers purpose, selection vs. siblings, hardware gating factors, and a sketch of the return payload. An agent has everything needed to call it and interpret results.

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 the schema already documents all four parameters. The Args block largely duplicates the schema text verbatim; the parenthetical material implications (enclosure for ABS/ASA/Nylon/PC, direct drive for TPU) appear in the schema descriptions too, so little meaning is added beyond structured fields.

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?

States a specific verb and resource ("recommend material for engineering/functional parts") plus the axes it optimizes for (strength, heat, environment). The dedicated "Which material tool to use" block explicitly distinguishes it from the three closest siblings: recommend_material and suggest_material_for_order.

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 an explicit routing table with the selecting condition for each alternative: engineering specs → this tool, quick intent-based pick for your own printer → recommend_material, ordering from a service → suggest_material_for_order. No inference required to choose correctly.

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