Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

get_recovery_gcode_steps

Read-only

Retrieve the G-code and commands needed to execute a recovery for a given session, so agents can recover a failed or interrupted 3D print.

Instructions

Get the G-code/commands for executing a recovery.

        Args:
            session_id: The session_id to get steps for.

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

Input Schema

NameRequiredDescriptionDefault
session_idYesThe session_id to get steps for.

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 to get steps for."
  2. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds no behavioral context such as whether the session must be active, what the returned commands look like, or any permission/lifecycle requirements; it merely restates the purpose.

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 purpose is front-loaded in one sentence and the parameter note is short. The indented 'Args:' block is redundant with the schema and slightly unpolished, but there is no substantive verbosity.

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?

For a simple one-parameter read-only retrieval, the description identifies the operation and parameter. However, with no output schema, it does not explain the shape or meaning of the returned G-code steps, and it gives no recovery-session context, leaving a meaningful gap.

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 single session_id parameter is fully documented in the schema. The description repeats 'The session_id to get steps for' without adding format, source, or validation details, so the schema carries the semantic 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?

The description uses a specific verb ('Get') and resource ('G-code/commands for executing a recovery') and names session_id as the target, so the operation is clear. It does not distinguish this retrieval from related recovery siblings such as generate_recovery_gcode or get_recovery_plan, so it falls short of a 5.

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

Usage Guidelines2/5

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

It gives no explicit when-to-use guidance, prerequisites, or alternatives. The phrase 'for executing a recovery' implies a recovery context, but it does not tell an agent when to choose this versus generating G-code or fetching a recovery plan.

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