Kiln

Overview Schema Source Related Servers Discussions Admin

suggest_material_for_order

Read-only

Recommends materials and printing technologies for fulfillment print orders based on use case, budget, and needs like strength, detail, weather resistance, or food safety. Returns ranked options.

Instructions

Suggest a material when ordering a print from a fulfillment provider.

        Use this when routing a print job to a fulfillment provider
        and need to pick the right material + technology for the order.

        **Which material tool to use:**

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

        Args:
            use_case: What the part is for. Options: decorative, functional,
                mechanical, prototype, miniature, jewelry, enclosure, wearable,
                outdoor, food_safe.
            budget: Price preference: "budget", "mid", or "premium". Empty = any.
            need_weather_resistant: Only recommend weather-resistant materials.
            need_food_safe: Only recommend food-safe materials.
            need_high_detail: Prefer high-detail materials (SLA/MJF).
            need_high_strength: Prefer high-strength materials (SLS/MJF).

        Returns ranked material recommendations with technology, reasoning,
        price tier, and which fulfillment provider to use.

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": {
      "use_case": "<use_case>"
    },
    "name": "suggest_material_for_order"
  }
}

Input Schema

Name	Required	Description
`budget`	No	Price preference: "budget", "mid", or "premium". Empty = any. Default: "".
`use_case`	Yes	What the part is for. Options: decorative, functional, mechanical, prototype, miniature, jewelry, enclosure, wearable, outdoor, food_safe.
`need_food_safe`	No	Only recommend food-safe materials. Default: false.
`need_high_detail`	No	Prefer high-detail materials (SLA/MJF). Default: false.
`need_high_strength`	No	Prefer high-strength materials (SLS/MJF). Default: false.
`need_weather_resistant`	No	Only recommend weather-resistant materials. Default: false.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv1.5.1Nov 5, 2026

changedInput schema / properties / budget / description

Previous value: -"Default: \"\"."New value: +"Price preference: \"budget\", \"mid\", or \"premium\". Empty = any. Default: \"\"."

changedInput schema / properties / need_food_safe / description

Previous value: -"Default: false."New value: +"Only recommend food-safe materials. Default: false."

changedInput schema / properties / need_high_detail / description

Previous value: -"Default: false."New value: +"Prefer high-detail materials (SLA/MJF). Default: false."

changedInput schema / properties / need_high_strength / description

Previous value: -"Default: false."New value: +"Prefer high-strength materials (SLS/MJF). Default: false."

changedInput schema / properties / need_weather_resistant / description

Previous value: -"Default: false."New value: +"Only recommend weather-resistant materials. Default: false."

addedInput schema / properties / use_case / description

Added value: +"What the part is for. Options: decorative, functional, mechanical, prototype, miniature, jewelry, enclosure, wearable, outdoor, food_safe."

Changed10 schema fields changedv1.5.0Oct 23, 2026
- removedInput schema / properties / budget / default
```
Removed value: -""
```
- addedInput schema / properties / budget / description
```
Added value: +"Default: \"\"."
```
- removedInput schema / properties / need_food_safe / default
```
Removed value: -false
```
- addedInput schema / properties / need_food_safe / description
```
Added value: +"Default: false."
```
- removedInput schema / properties / need_high_detail / default
```
Removed value: -false
```
- addedInput schema / properties / need_high_detail / description
```
Added value: +"Default: false."
```
- removedInput schema / properties / need_high_strength / default
```
Removed value: -false
```
- addedInput schema / properties / need_high_strength / description
```
Added value: +"Default: false."
```
- removedInput schema / properties / need_weather_resistant / default
```
Removed value: -false
```
- addedInput schema / properties / need_weather_resistant / description
```
Added value: +"Default: false."
```
First observedv0.1.0Jul 4, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile needs no restating. The description adds value by disclosing the result shape ('ranked material recommendations with technology, reasoning, price tier, and which fulfillment provider to use'), which matters because no output schema exists. It does not say whether provider choice is merely reported or committed, which would have completed the picture.

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

Conciseness3/5

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

The routing selector is well placed and front-loaded, and the Returns line earns its place given there is no output schema. However, the six-line Args block duplicates the schema one-to-one and could be cut entirely, making roughly a third of the text redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Six parameters with only one required are fully documented, and the description compensates for the missing output schema by describing the ranked return. What remains unstated is the ranked-vs-filtered semantics of the boolean needs (do they filter or just prefer?) and whether the fulfillment provider output is advisory, which an agent routing a real order would want.

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%, and the Args block in the description restates the schema descriptions verbatim, including the same enumerated use_case values and the same budget options. No format, defaulting, or interaction semantics (e.g., what happens when need_high_detail and need_high_strength conflict) are added beyond the schema, so the baseline 3 applies.

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 ('Suggest a material when ordering a print from a fulfillment provider') plus the exact context of routing a print job. That is enough to distinguish it from the three sibling material tools without inspecting any schema.

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?

Explicitly names the alternative tools and the condition that selects each: 'Designing a part and need engineering specs? → recommend_design_material' and 'Quick intent-based pick for your own printer? → recommend_material'. When-to-use and when-not-to-use are both covered.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server