Kiln

Overview Schema Source Related Servers Discussions Admin

update_interception_telemetry

Destructive

Push live telemetry snapshots to an active interception session to enable rule-based evaluation of device state, including temperature thresholds and flow anomalies during printing.

Instructions

Push a telemetry snapshot to an active interception session.

Telemetry is used by rules that evaluate live device state
(temperature thresholds, thermal runaway detection, flow anomalies).
Call this periodically during printing (e.g. every few seconds).

Args:
    session_id: Active session ID.
    hotend_temp: Current hotend temperature (C).
    hotend_target: Target hotend temperature (C).
    bed_temp: Current bed temperature (C).
    bed_target: Target bed temperature (C).
    position_x: Current X position (mm).
    position_y: Current Y position (mm).
    position_z: Current Z position (mm).
    feedrate: Current feedrate (mm/min).
    flow_rate_pct: Flow rate percentage (100 = normal).
    fan_speed_pct: Fan speed percentage.
    current_layer: Current layer number.
    elapsed_seconds: Elapsed print time (seconds).
    filament_used_mm: Filament consumed (mm).

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>"
    },
    "name": "update_interception_telemetry"
  }
}

Input Schema

Name	Required	Description
`bed_temp`	No	Current bed temperature (C).
`feedrate`	No	Current feedrate (mm/min).
`bed_target`	No	Target bed temperature (C).
`position_x`	No	Current X position (mm).
`position_y`	No	Current Y position (mm).
`position_z`	No	Current Z position (mm).
`session_id`	Yes	Active session ID.
`hotend_temp`	No	Current hotend temperature (C).
`current_layer`	No	Current layer number.
`fan_speed_pct`	No	Fan speed percentage.
`flow_rate_pct`	No	Flow rate percentage (100 = normal).
`hotend_target`	No	Target hotend temperature (C).
`elapsed_seconds`	No	Elapsed print time (seconds).
`filament_used_mm`	No	Filament consumed (mm).

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedv1.5.1Nov 5, 2026
- addedInput schema / properties / bed_target / description
```
Added value: +"Target bed temperature (C)."
```
- addedInput schema / properties / bed_temp / description
```
Added value: +"Current bed temperature (C)."
```
- addedInput schema / properties / current_layer / description
```
Added value: +"Current layer number."
```
- addedInput schema / properties / elapsed_seconds / description
```
Added value: +"Elapsed print time (seconds)."
```
- addedInput schema / properties / fan_speed_pct / description
```
Added value: +"Fan speed percentage."
```
- addedInput schema / properties / feedrate / description
```
Added value: +"Current feedrate (mm/min)."
```
- addedInput schema / properties / filament_used_mm / description
```
Added value: +"Filament consumed (mm)."
```
- addedInput schema / properties / flow_rate_pct / description
```
Added value: +"Flow rate percentage (100 = normal)."
```
- addedInput schema / properties / hotend_target / description
```
Added value: +"Target hotend temperature (C)."
```
- addedInput schema / properties / hotend_temp / description
```
Added value: +"Current hotend temperature (C)."
```
- addedInput schema / properties / position_x / description
```
Added value: +"Current X position (mm)."
```
- addedInput schema / properties / position_y / description
```
Added value: +"Current Y position (mm)."
```
- addedInput schema / properties / position_z / description
```
Added value: +"Current Z position (mm)."
```
- addedInput schema / properties / session_id / description
```
Added value: +"Active session ID."
```
Changed13 schema fields changedv1.5.0Oct 23, 2026
- removedInput schema / properties / bed_target / default
```
Removed value: -null
```
- removedInput schema / properties / bed_temp / default
```
Removed value: -null
```
- removedInput schema / properties / current_layer / default
```
Removed value: -null
```
- removedInput schema / properties / elapsed_seconds / default
```
Removed value: -null
```
- removedInput schema / properties / fan_speed_pct / default
```
Removed value: -null
```
- removedInput schema / properties / feedrate / default
```
Removed value: -null
```
- removedInput schema / properties / filament_used_mm / default
```
Removed value: -null
```
- removedInput schema / properties / flow_rate_pct / default
```
Removed value: -null
```
- removedInput schema / properties / hotend_target / default
```
Removed value: -null
```
- removedInput schema / properties / hotend_temp / default
```
Removed value: -null
```
- removedInput schema / properties / position_x / default
```
Removed value: -null
```
- removedInput schema / properties / position_y / default
```
Removed value: -null
```
- removedInput schema / properties / position_z / default
```
Removed value: -null
```
First observedv0.1.0Jul 4, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare this is a non-read-only, closed-world operation with destructiveHint=true. The description adds useful context by explaining that telemetry feeds live rules for thermal runaway and flow anomalies and should be sent repeatedly, though it does not clarify what 'destructive' means here or how invalid/inactive sessions behave.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and cadence guidance are front-loaded and easy to scan. However, the 14-line Args block duplicates the already-complete schema and does not mark which fields are optional, so a meaningful portion of the text does not earn its place.

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 tool has an output schema and detailed annotations, and the description covers the core purpose, cadence, and all telemetry fields. It is nearly complete, though it could say what happens if the session is not active or how partial/null telemetry values are interpreted.

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%, so the baseline is 3. The Args block largely restates the schema descriptions verbatim and does not add syntax, optionality, or null-handling guidance beyond what the schema already provides.

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 first sentence gives a specific verb and resource: 'Push a telemetry snapshot to an active interception session.' That clearly distinguishes this tool from siblings such as get_interception_status, list_interception_sessions, and intercept_gcode_command.

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 explicitly says to call this periodically during printing, with a concrete cadence example of every few seconds. It also scopes usage to an active session, but it does not name alternatives or state when not to use it.

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

Deploy Server