Skip to main content
Glama

set_temperature

Set target temperatures for the hotend and heated bed in Celsius, optionally for a specific printer. Pass 0 to turn a heater off, or omit a value to leave it unchanged.

Instructions

Set the target temperature for the hotend (tool) and/or heated bed.

Args:
    tool_temp: Target hotend temperature in Celsius.  Pass ``0`` to turn
        the heater off.  Omit or pass ``null`` to leave unchanged.
    bed_temp: Target bed temperature in Celsius.  Pass ``0`` to turn
        the heater off.  Omit or pass ``null`` to leave unchanged.
    printer_name: Which printer to heat.  Omit for the default printer,
        which is what this did before it could be aimed — so asking to
        preheat a second machine heated the default one instead.  The
        safety ceiling follows the named machine: a printer with no
        declared model is held to the unknown-printer limit rather than
        to the default printer's, which may be the more permissive of
        the two.

At least one of ``tool_temp`` or ``bed_temp`` must be provided.

Common PLA temperatures: tool 200-210C, bed 60C.
Common PETG temperatures: tool 230-250C, bed 80-85C.
Common ABS temperatures: tool 240-260C, bed 100-110C.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bed_tempNo
tool_tempNo
printer_nameNo
Install Server

TDQS

A4.7/5.0
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 does an excellent job. It discloses the off-by-zero behavior, the leave-unchanged on null, the historical default-printer pitfall, and the safety-ceiling rule based on the named printer's declared model. This goes far beyond a typical setter and gives the agent crucial behavioral expectations.

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?

The description is well-structured with a clear purpose statement, Args section, and common temperature ranges. Every sentence provides useful information, and the length is justified by the complexity of the tool's safety and multi-printer behavior. There is no fluff or repetition.

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?

The description covers the tool's purpose, parameters, edge cases, and even includes practical temperature guides. However, it does not mention the return value or failure/error behavior, and since there is no output schema, the agent might not know what to expect as a result. Still, for a setter tool, this is a minor gap given the strong behavioral coverage.

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 description coverage is 0%, and the description compensates fully. Each parameter is explained in detail: tool_temp and bed_temp semantics (0 turns off, null leaves unchanged), and printer_name's role in targeting and safety calculations. The 'at least one' constraint is also explicitly stated, adding meaning that the schema alone does not provide.

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, specific verb and resource: 'Set the target temperature for the hotend (tool) and/or heated bed.' This unambiguously distinguishes it from sibling tools like set_fan or set_speed_profile, and clearly states both the hotend and bed as targets.

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?

The description explains when to use the tool (to set hotend/bed temperatures) and provides critical usage context: the requirement that at least one temperature be provided, the 0-to-turn-off behavior, and the multi-printer behavior with the default printer and safety-ceiling gotcha. It does not explicitly name alternative tools for exclusions, but the context is clear enough.

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

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