Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

load_safety_interception_rules

Load safety rules for a 3D printer into an active session to enforce temperature limits and block unsafe commands. Use it to reset or refresh the session's safety protection.

Instructions

Load safety-profile rules for a printer into an active session.

Generates rules from the printer's safety profile (temperature
limits, feedrate caps, blocked commands) and adds them to the
session.  Use this to reset or refresh safety rules.

Args:
    session_id: Target session ID.
    printer_name: The printer, as registered in Kiln or by its model
        key (e.g. ``"bambu_a1"``); a model key gives the fullest rule
        set, a nickname Kiln cannot resolve to a model loads generic
        limits and says so in ``coverage_warnings``.

AGENT CONTRACT: relay any ``coverage_warnings`` to the user verbatim
-- they mean the loaded rule set protects less than a full one.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "session_id": "<session_id>",
      "printer_name": "<printer_name>"
    },
    "name": "load_safety_interception_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYesTarget session ID.
printer_nameYesThe printer, as registered in Kiln or by its model key (e.g. ``"bambu_a1"``); a model key gives the fullest rule set, a nickname Kiln cannot resolve to a model loads generic limits and says so in ``coverage_warnings``.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.1
    • addedInput schema / properties / printer_name / description
      Added value: +"The printer, as registered in Kiln or by its model key (e.g. ``\"bambu_a1\"``); a model key gives the fullest rule set, a nickname Kiln cannot resolve to a model loads generic limits and says so in ``coverage_warnings``."
    • addedInput schema / properties / session_id / description
      Added value: +"Target session ID."
  2. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations (non-read-only, non-destructive, closed-world), the description discloses that rules are generated from the profile and added to the session, and that falling back to a nickname yields generic limits flagged in coverage_warnings. The AGENT CONTRACT to relay warnings verbatim is genuinely useful behavioral guidance. It stops short of saying whether pre-existing session rules are replaced or merely appended.

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?

Front-loaded with purpose, then behavior, then an explicit agent contract; the sections are well delineated. The Args section largely duplicates the schema and could be trimmed without loss.

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?

With an output schema present and annotations covering side-effect profile, the description need not explain return values, and coverage_warnings handling is already called out. The only material gap is the lack of clarity on whether existing session rules are replaced or accumulated.

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 description coverage is 100% and the description's Args block reproduces the schema text nearly verbatim, so no meaning is added. The one nuance (model key vs. nickname) is already present in the printer_name schema description, so the description earns only the baseline.

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 (load safety-profile rules into a session) and explains what the resulting rules contain (temperature limits, feedrate caps, blocked commands). It never names or contrasts a sibling such as add_interception_rule or add_safety_profile, so differentiation is left to the caller.

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?

'Use this to reset or refresh safety rules' gives a clear triggering context for the tool. There is no explicit when-not guidance, no mention of when to use add_interception_rule or add_safety_profile instead, and no statement of preconditions (e.g. an active interception session must exist).

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