Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

pipeline_pause

Destructive

Pause a running pipeline at the next step boundary so the current step finishes before pausing; use pipeline_resume to continue.

Instructions

Pause a running pipeline at the next step boundary.

        The pipeline will finish the current step and then pause before
        starting the next one.  Use ``pipeline_resume`` to continue.

        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_pause"
  }
}

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

A3.7/5.0
Behavior3/5

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

The description adds real behavior beyond the annotations: the pause is deferred, letting the current step finish before halting, which matters for timing expectations. However, it never addresses the destructiveHint=true annotation or states whether pipeline state is preserved and whether repeated calls are idempotent when already paused, leaving the safety profile unexplained.

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 behavioral statement is front-loaded and the resume pointer is placed immediately after it, so the key information comes first. The trailing Args section duplicates the input schema and could be dropped without loss.

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?

For a single-parameter lifecycle tool with no output schema, the description covers what happens, when the pause takes effect, and how to undo it, which is nearly everything an agent needs. The remaining gap is the unaddressed destructive flag and the result of pausing an already-paused execution.

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?

With one parameter at 100% schema description coverage, the schema already documents `execution_id`, and the description's Args block only restates the schema text verbatim. No extra meaning (format, source of the ID, behavior on an invalid ID) is added, so baseline 3 applies.

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 opening sentence names a specific verb, resource, and timing scope ('Pause a running pipeline at the next step boundary'), which is far more precise than the bare name. The reference to `pipeline_resume` for the inverse operation further separates it from the pipeline family (abort, retry_step, status).

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?

It points to `pipeline_resume` for continuation, which implies the pause/resume pairing, but gives no guidance on when to pause rather than `pipeline_abort` or `pipeline_retry_step`, nor any prerequisite (e.g. execution must be running). Usage context is implied rather than stated.

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