Skip to main content
Glama

update_interception_telemetry

Push telemetry snapshots to an active interception session to enable real-time device state monitoring for printing rules.

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).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bed_tempNo
feedrateNo
bed_targetNo
position_xNo
position_yNo
position_zNo
session_idYes
hotend_tempNo
current_layerNo
fan_speed_pctNo
flow_rate_pctNo
hotend_targetNo
elapsed_secondsNo
filament_used_mmNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

With no annotations, the description carries full burden. It discloses action and purpose, and implies session must be active, but does not discuss side effects, validation, or failure modes. Lacks depth on what happens if session is invalid.

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?

Very concise and well-structured: action statement, purpose explanation, usage guidance, then parameter list. No wasted words, information front-loaded.

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?

Given 14 parameters and no annotation coverage, the description provides complete parameter details and usage context. Does not describe output schema or prerequisites beyond active session, but the presence of output schema reduces need for return value explanation.

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

Parameters4/5

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

Schema coverage is 0%, but the description compensates by listing all 14 parameters with explicit units and context (e.g., 'Current hotend temperature (C)'). Adds meaning beyond type/name, though some parameters could have more detail.

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 pushes a telemetry snapshot to an active interception session, using specific verbs ('Push') and resource ('telemetry snapshot'). It distinguishes from siblings like intercept_gcode_command by focusing on telemetry data for rule evaluation.

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?

Explicitly advises periodic calls during printing with example frequency ('every few seconds'), and explains why telemetry is needed (for rules evaluating device state). Does not mention when not to use or alternatives, but provides sufficient context.

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