Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

list_ingested_materials

Read-only

Browse and filter your ingested 3D printing materials library by brand or type, or fetch the full specification for a specific material ID.

Instructions

Browse your ingested-materials library, or fetch one full spec.

Needs Kiln Business.

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_ingested_materials"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandNoFilter, e.g. ``"Bambu Lab"``. Default: "".
material_idNoReturn the full spec for this id instead of a list. Default: "".
material_typeNoFilter, e.g. ``"pla"``. Default: "".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.5.1
    • changedInput schema / properties / brand / description
      Previous value: -"Default: \"\"."New value: +"Filter, e.g. ``\"Bambu Lab\"``. Default: \"\"."
    • changedInput schema / properties / material_id / description
      Previous value: -"Default: \"\"."New value: +"Return the full spec for this id instead of a list. Default: \"\"."
    • changedInput schema / properties / material_type / description
      Previous value: -"Default: \"\"."New value: +"Filter, e.g. ``\"pla\"``. Default: \"\"."
  2. Addedv1.5.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish read-only, non-destructive, closed-world behavior. The description adds the Kiln Business entitlement requirement, which is valuable, but it does not explain pagination, result limits, or how filters interact with material_id when fetching a single spec.

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 with no wasted wording. The primary capability is front-loaded, and the entitlement requirement is clearly separated.

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 read-only listing/fetch tool with full schema descriptions and explicit annotations, the definition covers the core capability and tier requirement. It is somewhat incomplete in not differentiating itself from other material-related tools or describing return shape, but no output schema exists and the tool is straightforward.

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%, so the schema already documents brand, material_type, and the material_id mode switch. The description reinforces the material_id behavior by saying 'fetch one full spec,' but adds little beyond what the schema already states.

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 states a specific resource and two modes: browsing an ingested-materials library or fetching one full spec. It does not explicitly distinguish this tool from nearby siblings such as list_materials, get_material, or read_material_datasheet, so it stops short of a 5.

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 'Needs Kiln Business' gives a useful prerequisite, and 'or fetch one full spec' implies the material_id mode. However, there is no explicit guidance on when to use this instead of the many sibling material-listing or material-retrieval tools.

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