Skip to main content
Glama
codeofaxel

Kiln

by codeofaxel
OverviewSchemaRelated ServersScoreDiscussions
Python

check_printer_material_compatibility

Check whether a specific printer can print a given material, or view its full material compatibility matrix. Get compatibility status, required upgrades, and practical notes.

Instructions

Check if a specific printer can handle a material.

        Returns compatibility status (compatible / needs_upgrade /
        not_compatible), any required hardware upgrades (enclosure,
        hardened nozzle, dry box), and practical notes.

        When no material is specified, returns the full compatibility
        matrix for the printer across all known materials.

        Use this when a user asks "can my Ender 3 print nylon?" or
        "what materials work on my Bambu A1 Mini?"

        Args:
            printer: Printer model ID (e.g. "ender3", "bambu_x1c",
                "prusa_mk4", "voron_2"). Use underscores, lowercase.
            material: Optional material to check (e.g. "nylon", "abs").
                If omitted, returns all materials for this printer.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
printerYes
materialNo

Tool Definition Quality

A4.1/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden. It describes the query nature but does not disclose any behavioral traits such as side effects, destructiveness, permissions, or rate limits. For a read-like operation this is acceptable but missing explicit safety cues.

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 description is well-organized with line breaks, bullet-like lists, and front-loaded purpose. It includes examples and parameter details in a structured format. Slightly verbose due to the 'Args:' section, but overall efficient.

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

Completeness5/5

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

For a tool with two parameters, no output schema, and no annotations, the description covers inputs, outputs (status, upgrades, notes), and usage context for both parameterized and non-parameterized calls. It is fully complete for an agent to understand and invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, yet the description fully explains both parameters: printer with format guidance and examples, material with behavior when omitted. This adds critical meaning beyond the bare schema, enabling correct parameter usage.

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?

The description clearly states the tool checks printer-material compatibility, specifies return types (compatibility status, upgrades, notes), and distinguishes itself from sibling tools like 'check_printer_material_support' and 'get_compatible_materials' by detailing the output structure and the behavior when no material is specified.

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

Usage Guidelines4/5

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

Provides concrete usage examples ('can my Ender 3 print nylon?') and explains the behavior when material is omitted, giving clear context. Lacks explicit when-not-to-use or alternatives, but the guidance is sufficient for appropriate invocation.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/codeofaxel/kiln'

If you have feedback or need assistance with the MCP directory API, please join our Discord server