Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

pipeline_abort

Destructive

Abort a running or paused pipeline immediately while preserving completed steps in the result. Provide the execution ID to stop further processing.

Instructions

Abort a running or paused pipeline.

        Immediately marks the pipeline as aborted. Any completed steps
        are preserved in the result.

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

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.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds real value beyond that: the effect is immediate and completed steps are retained in the result, which tells an agent this is irreversible for in-flight work but not data-destroying.

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?

Two short, front-loaded sentences put the effect and the data-retention consequence first. The trailing Args block duplicates the schema and could be dropped, but the overall footprint is small.

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 destructive one-parameter mutation with no output schema, the description covers effect, immediacy, and result preservation, but leaves open what happens to partially executing steps and whether calling it on an already-aborted or unknown execution errors or no-ops.

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% for the single execution_id parameter, and the description's Args line restates the schema text verbatim ('The pipeline execution ID') without adding format, sourcing, or validation detail. Baseline 3 applies.

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?

States a specific verb (abort) and resource (pipeline), and the qualifier 'running or paused' scopes which pipelines are eligible. It implicitly contrasts with the neighboring pipeline_pause/pipeline_resume/pipeline_retry_step tools, though it never names them.

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?

The phrase 'running or paused pipeline' implies the precondition for calling it, but there is no explicit when-to-use rule, no statement of what to do instead (pause vs abort vs retry_step), and no guidance for already-finished or nonexistent executions.

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