Skip to main content
Glama

select_printer_variant

Declare your printer model and hardware variant so Kiln can supply verified temperature limits. Select the matching variant to replace guessed limits with curated, manufacturer-backed ceilings.

Instructions

Declare which curated hardware variant your machine actually is.

        This is how an operator with a modified printer gets an accurate
        ceiling WITHOUT typing one.  You say which hardware you have; Kiln
        supplies the limit from curated, manufacturer-sourced data.  There
        is no argument here that accepts a temperature, which is the point:
        a limit Kiln enforces is always a limit Kiln verified.

        Check ``requires`` on the variant first — a ceiling is only true if
        its preconditions are met.  Several variants need a firmware change
        as well as the part, and selecting the variant is your statement
        that you have done both.  Kiln cannot check your hardware remotely.

        The declaration stays on this machine.  It is never uploaded or
        pooled, and it is ignored entirely on hosted multi-tenant
        deployments, where "this machine" has no single owner.

        Args:
            printer_model: Printer identifier (e.g. ``"ender3"``).
            variant_id: Variant to declare, from ``list_printer_variants``.
                Pass ``""`` to go back to the as-shipped profile.
        

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
variant_idNo
printer_modelYes
Behavior5/5

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

With no annotations provided, the description carries the full burden, and it excels: it discloses that the declaration is local-only, never uploaded or pooled, ignored on multi-tenant deployments, and that Kiln cannot remotely verify the hardware. It also explains that selecting a variant asserts firmware/part prerequisites have been satisfied.

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 long but front-loaded with the core purpose and each paragraph adds substantive caveats or behavioral details. Some phrasing could be tightened, but every section earns its place.

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?

The description is complete for a tool with no annotations or output schema: it covers when to use it, prerequisites, side effects, persistence, multi-tenant behavior, parameter meaning, and how to reset. The return behavior is sufficiently implied by 'Kiln supplies the limit.'

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?

Despite 0% schema description coverage, the description fully explains both parameters: printer_model is a printer identifier with an example, and variant_id comes from list_printer_variants with '' meaning return to the as-shipped profile. This adds real semantic meaning beyond the raw schema.

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 opens with a clear verb and resource: 'Declare which curated hardware variant your machine actually is.' It further explains that Kiln supplies an enforced ceiling from curated data and explicitly distinguishes itself from a tool that accepts a temperature value.

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?

It gives strong usage context: an operator with a modified printer uses this to get an accurate ceiling without typing one, and should check the variant's 'requires' first. It points to list_printer_variants for valid variant IDs and warns that selection is a statement that preconditions are met, though it does not explicitly name alternative tools besides that.

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