Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

get_material_properties

Read-only

Retrieve a material's public safety and printing-property profile by material ID, including thermal, chemical-safety, and process-design data for 3D printing decisions.

Instructions

Get a material's public safety and printing-property profile.

Returns the public thermal, chemical-safety, and process-design floor.
Deeper engineering questions are answered one at a time by Kiln's
servers.

Args:
    material_id: Material key (e.g. ``"petg"``, ``"tpu"``, ``"cf_pla"``).
        Case-insensitive.

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": {
      "material_id": "<material_id>"
    },
    "name": "get_material_properties"
  }
}

Input Schema

NameRequiredDescriptionDefault
material_idYesMaterial key (e.g. ``"petg"``, ``"tpu"``, ``"cf_pla"``). Case-insensitive.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / material_id / description
      Added value: +"Material key (e.g. ``\"petg\"``, ``\"tpu\"``, ``\"cf_pla\"``). Case-insensitive."
  2. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover readOnly/non-destructive/closed-world, and the description adds the meaningful qualifier that the returned data is a public "floor" of thermal, chemical-safety, and process-design information rather than full engineering data. That tells the agent to expect limited depth and to escalate deeper questions, which is real value beyond the annotations.

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 purpose and scope land in the first sentence, with supporting depth in the two that follow. The Args block duplicates the schema and is redundant, but overall the text is short and front-loaded with no filler.

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?

A one-parameter, read-only lookup is fully actionable with the given information: the resource, the key format, and the depth of the returned profile are all stated. The absence of an output schema means return contents are described only loosely, but the summary of thermal/chemical/process-design data is adequate for this complexity.

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 coverage is 100% and the Args block simply restates the schema description verbatim, including the examples and the case-insensitive note. The description therefore adds no parameter meaning beyond the structured input schema; baseline 3 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+resource ("Get a material's ... profile") and qualifies the scope as "public safety and printing-property", which separates it from deeper material tools like get_material_slicing_profile or get_material_design_profile. It never names a sibling explicitly, so the differentiation is inferable rather than stated.

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

Usage Guidelines3/5

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

The line "Deeper engineering questions are answered one at a time by Kiln's servers" implies this is the shallow baseline lookup and that deeper queries belong elsewhere, which is useful routing context. However, no alternative tool is named and there is no explicit when-not-to-use statement, so an agent must infer the boundary.

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