Skip to main content
Glama
Sign In
jobd

jobd

by musharna
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

jobd_preempt

Preempt a running preemptible job by signaling its worker with SIGTERM and a grace period, moving it to 'preempted'. Refuses jobs that aren't preemptible or running.

Instructions

Preempt a running/assigned preemptible job (worker SIGTERMs with grace; final state 'preempted'). Refused if not preemptible or not running.

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": {
      "job_id": "<job_id>"
    },
    "name": "jobd_preempt"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.47
    • addedInput schema / additionalProperties
      Added value: +false
  2. Addedv0.5.36
  3. Removedv0.5.35
  4. First observedv0.5.5

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, this description carries the behavioral burden and does well: it discloses the worker side effect (SIGTERM with grace), the terminal state ('preempted'), and refusal conditions. There is a minor ambiguity between 'assigned' being preemptable and 'refused if not running', but overall the key behaviors are transparent.

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 entire description is one dense sentence with no filler. It front-loads the core action and immediately follows with behavioral consequences and refusal criteria; every phrase earns its place.

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 tool with no output schema, the description supplies the essential invocation context: what happens, what the final state is, and when the call fails. It does not describe the return payload, but given no output schema and simple side effects, the description is reasonably complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but the sole parameter job_id is a simple integer whose meaning is obvious from the description. The description adds semantic constraints on which job_ids are valid (preemptible, running/assigned), which is useful context beyond the bare schema.

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 uses a specific verb ('Preempt') and a precise resource ('a running/assigned preemptible job'), and it names the distinguishing final state ('preempted'). It also implicitly differentiates from jobd_cancel by restricting preemption to preemptible jobs, so an agent can tell which sibling applies.

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 clearly states when the tool is valid ('running/assigned preemptible job') and when it will be refused ('if not preemptible or not running'). It does not explicitly name an alternative such as jobd_cancel for non-preemptible jobs, which keeps it just short of a 5.

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