Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

confirm_print_recovery

Destructive

Approve a pending 3D print recovery plan so it proceeds from awaiting confirmation to execution when human sign-off is required.

Instructions

Confirm that a recovery plan should proceed.

        For plans requiring human confirmation, transitions from
        ``awaiting_confirmation`` to ``executing``.

        Args:
            session_id: The session_id to confirm.

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

Input Schema

NameRequiredDescriptionDefault
session_idYesThe session_id to confirm.

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 confirm."
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

The description adds meaningful behavioral context beyond the annotations by explaining the state machine transition (awaiting_confirmation to executing). However, it does not explain why destructiveHint is true or what the consequences of confirming are (e.g., that execution becomes irreversible), which would be valuable for a destructive action.

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 description is short and front-loads the core action and state transition. The Args section is somewhat redundant with the schema but not harmful. It is appropriately sized for a single-parameter tool.

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 state-transition tool, the description covers the essential action and transition. It omits what happens if the session is not in awaiting_confirmation, and does not elaborate on the destructive nature flagged in annotations, leaving a modest 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 coverage is 100% and the single parameter is fully documented in the schema. The description's 'session_id: The session_id to confirm' merely restates the schema without adding format, source, or validation details. Baseline 3 is appropriate.

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 states a specific verb and resource: 'Confirm that a recovery plan should proceed,' and clarifies the state transition from awaiting_confirmation to executing. This distinguishes it reasonably from siblings like plan_print_recovery or start_print_recovery, though it does not name them explicitly.

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?

It gives a clear condition for use: 'For plans requiring human confirmation.' This tells the agent when the tool applies. However, it does not explicitly contrast with alternatives such as cancel_print_recovery or start_print_recovery, leaving some routing inference to the agent.

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