Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

get_material_warnings

Read-only

Retrieve warnings for printing a specific material on a chosen printer to identify potential issues before starting a print.

Instructions

Get warnings about printing a specific material on a printer.

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": {
      "printer_id": "<printer_id>",
      "material": "<material>"
    },
    "name": "get_material_warnings"
  }
}

Input Schema

NameRequiredDescriptionDefault
materialYesFilament material (e.g. "PLA", "PETG", "Nylon").
printer_idYesThe printer identifier.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.1
    • addedInput schema / properties / material / description
      Added value: +"Filament material (e.g. \"PLA\", \"PETG\", \"Nylon\")."
    • addedInput schema / properties / printer_id / description
      Added value: +"The printer identifier."
  2. Addedv1.5.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description's one genuine addition beyond that is the Kiln Pro tier requirement, which is real gating context an agent needs, but it says nothing about what warnings look like, how severe they may be, or whether an empty result is meaningful.

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?

Two short sentences, front-loaded with the action and resource, followed by the only blocking precondition. Nothing is redundant or padded.

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?

For a simple two-parameter read-only lookup with full schema coverage and complete annotations, the description covers the essentials plus the tier gate. The remaining shortfall is routing: in a family of a dozen material/printer compatibility tools, it does not help the agent decide this is the right one.

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 both required parameters documented in the schema including an example material list (PLA, PETG, Nylon). The description adds no meaning beyond that, so the baseline 3 for fully-described schemas applies.

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?

States a specific verb and resource: warnings about printing a given material on a given printer, which is more precise than the bare name. It does not distinguish itself from the many closely related siblings such as check_printer_material_support, check_printer_material_compatibility, or check_material_match, so an agent cannot tell from the description alone which of these to pick.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only usage-relevant statement is the prerequisite 'Needs Kiln Pro', which gates availability but says nothing about when to call this versus the numerous other material-compatibility tools. There are no exclusions, no alternatives named, and no indication of what question this tool answers that its siblings do not.

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