Skip to main content
Glama
claude-proxmox-controller

claude-proxmox-controller

stop_task

Destructive

Terminate a running Proxmox task started through this connector by supplying its host, UPID, and a reason for approval and logging.

Instructions

Stop a running task (one started through this connector).

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": {
      "host": "<host>",
      "upid": "<upid>",
      "reason": "<reason>"
    },
    "name": "stop_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYesThe host's id, from list_hosts.
upidYes
reasonYesWhy you are doing this, in a sentence. The user sees it in the approval window and in the log.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is covered structurally. The description adds the meaningful constraint that only connector-originated tasks are eligible, but says nothing about what happens to a task that is mid-flight (partial state, rollback, resumability) or what a second stop call does on an already-stopped task.

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?

A single short sentence with the operation front-loaded and the qualifying clause immediately after; no filler, no restatement of the title.

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, non-idempotent three-parameter mutation with no output schema, the description is minimally adequate — the annotations carry the danger signal and the parenthetical carries the scope. However it omits what is returned or how the caller learns the stop succeeded, and leaves the upid argument unexplained, which is a real gap for a required parameter.

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

Parameters2/5

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

Schema coverage is 67%: host and reason are described in-schema (host by reference to list_hosts, reason by its approval-window/log visibility), but 'upid' carries no description anywhere, and the tool description does not explain what identifier format or source an agent should supply. The description adds no parameter meaning of its own, leaving the most opaque argument undocumented.

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 pairs the specific verb "Stop" with the resource "running task" and adds a scoping qualifier that this applies only to tasks started through this connector, which usefully separates it from logging/inspection siblings like task_log. It does not name a sibling explicitly, so it lands just short of the top mark.

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 the scope note 'a running task (one started through this connector)' — an agent can infer it should not be used for tasks originating elsewhere. There is no explicit when-not guidance, no mention of prerequisites (e.g. host reachability, admin rights), and no named alternative for observing rather than cancelling work.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.