Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

stop_gcode_interception

Destructive

Stop an active G-code interception session using its session ID and return final session statistics.

Instructions

Stop a G-code interception session.

Args:
    session_id: The session ID returned by ``start_gcode_interception``.

Returns the final session stats.

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": "stop_gcode_interception"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYesThe session ID returned by ``start_gcode_interception``.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / session_id / description
      Added value: +"The session ID returned by ``start_gcode_interception``."
  2. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the terminating nature is known. The description adds that it returns final session stats, which is genuinely useful context, but says nothing about whether an in-progress print is affected, whether issued interception rules are discarded, or whether calling it twice errors.

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 core sentence is front-loaded and terse. The Args block duplicates the schema's own parameter description and is slightly wasteful, but the whole thing is still only a few lines with no padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so explaining return values is not required. However, for a destructive session-termination tool the description omits meaningful gaps: effect on an active print job, idempotency, and failure modes when the session_id is unknown or stale.

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 sole parameter is fully documented there; the description's Args block repeats that text verbatim without adding format, validation, or error semantics. Baseline 3 applies since the schema carries the load.

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?

Names a specific verb and resource ("Stop a G-code interception session") that is clearly distinct from lifecycle siblings such as start_gcode_interception and get_interception_status. It does not explicitly name the sibling alternatives, but the action itself is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the parameter note that session_id comes from start_gcode_interception sketches the start/stop lifecycle. There is no guidance on when to stop versus checking status via get_interception_status, nor any note on what to do if a session is already terminated.

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