Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

list_supported_materials

Read-only

Lists supported 3D-printing materials and their adaptive slicing constraints, including layer height limits, bridge parameters, and overhang angles, so you can choose valid print settings.

Instructions

List all materials with adaptive slicing profiles.

Returns material names with their key slicing constraints (layer height limits, bridge parameters, overhang angles).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_supported_materials"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/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 safety is covered. The description adds value beyond that by disclosing what is actually returned (material names plus layer height limits, bridge parameters, overhang angles) — important because there is no output schema.

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?

Two short sentences with the scope qualifier up front and the return contents following. Slight redundancy between 'List materials' and the following 'Returns material names', but nothing extraneous enough to trim.

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 parameterless, read-only listing tool with annotations covering the safety profile and no output schema, the description supplies the return shape an agent needs. It stops short of noting whether results are paginated or how many materials are typical, which is a minor gap.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the 4 baseline applies. No parameter information is missing or misleading.

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?

The description names a specific verb and resource ("List all materials") and narrows the scope with "with adaptive slicing profiles." That qualifier distinguishes it from the many other material-listing siblings (list_materials, list_available_materials, list_ingested_materials), though no sibling is named explicitly.

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 phrase "with adaptive slicing profiles" implies this is the entry point for adaptive-slicing workflows, and the sibling get_material_slicing_profile suggests a per-material follow-up. However, the description never states when to choose this over list_materials or get_material_slicing_profile, leaving routing to inference.

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