Skip to main content
Glama
Datris MCP Server

Datris MCP Server

kill_job

Terminate a running pipeline job by its pipeline token, interrupting the job thread and marking it cancelled; if approval is required, it returns a pending approval ID instead.

Instructions

Kill a running pipeline job by its pipeline token. The job thread will be interrupted and the job marked as cancelled. If this Datris instance's agent policy requires a person to approve this action, the call does NOT perform it: it returns status pending_approval with an approvalId. Tell the user it is waiting for approval in Datris, then poll get_approval with that id (pause with wait_seconds between polls) — do not re-issue the action.

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": {
      "pipeline_token": "<pipeline_token>"
    },
    "name": "kill_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoOptional one-line reason for this change, recorded in the platform's audit log and shown to anyone asked to approve it.
pipeline_tokenYesPipeline token of the running job to kill

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the mechanics (thread interrupted, job marked cancelled) and the policy-gated branch that returns status pending_approval plus an approvalId rather than performing the kill. It still does not state irreversibility, required permissions, or what a successful return looks like, leaving those to inference.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The primary action is front-loaded in the first sentence, and each following sentence handles a distinct contingency: cancellation semantics, the approval branch, and the polling instruction with the no-re-issue warning. There is no redundant restatement of the name or schema.

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 two-parameter mutation with no annotations and no output schema, the description covers the essential behaviors, including the unusual approval-return path that an agent would otherwise mishandle by retrying. The remaining gap is the success return shape and permission requirements, which are moderate rather than blocking.

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%, so both parameters, including reason being recorded in the audit log and shown to approvers, are already fully documented in structured data. The description adds only the qualifier that the token must belong to a running job, so the baseline of 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 description opens with a specific verb and resource, 'Kill a running pipeline job by its pipeline token', and limits scope to running jobs, which distinguishes it from the read-only status siblings like get_job_status and get_pipeline_status. An agent can identify the action without opening the schema.

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 states the condition for use (a running job identified by token) and gives explicit routing for the approval case: report pending_approval to the user, poll get_approval with the returned approvalId, pause with wait_seconds, and never re-issue the call. It does not explicitly exclude non-running or already-finished jobs or name a fallback for them, so it falls short of a full when/when-not treatment.

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