Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

pipeline_resume

Destructive

Resume a paused pipeline from its next unfinished step, continuing execution without restarting completed work.

Instructions

Resume a paused pipeline from where it stopped.

        Continues executing from the next unfinished step.

        Args:
            execution_id: The pipeline execution ID.

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": {
      "execution_id": "<execution_id>"
    },
    "name": "pipeline_resume"
  }
}

Input Schema

NameRequiredDescriptionDefault
execution_idYesThe pipeline execution ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / execution_id / description
      Added value: +"The pipeline execution ID."
  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 disclose that this is not read-only and has destructiveHint=true. The description adds useful behavior by saying it resumes from where it stopped and continues at the next unfinished step, but it does not explain side effects, failure behavior, or what makes the operation destructive.

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-loaded with the core action. The Args section duplicates the schema, so it is slightly redundant, but overall the wording is efficient.

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 tool with annotations covering the safety profile, the description is adequate. It still omits important behavioral details such as what happens if the pipeline is not paused, expected failure modes, and whether the operation is idempotent.

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?

The schema has 100% description coverage, and the single execution_id parameter is already documented in the schema. The description's Args section merely repeats that documentation and adds no extra meaning about the parameter.

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 gives a specific verb and resource: 'Resume a paused pipeline from where it stopped.' It also clarifies that execution continues from the next unfinished step, but it does not differentiate this tool from siblings such as pipeline_retry_step, pipeline_pause, or other resume-related tools.

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 implied by 'paused pipeline,' so an agent can infer this applies when a pipeline is paused. However, the description gives no explicit when-not guidance, prerequisites, or comparison to alternatives like pipeline_retry_step or pipeline_status.

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