Skip to main content
Glama
claude-proxmox-controller

claude-proxmox-controller

delete_backup_job

Destructive

Deletes a Claude-created backup job by ID, removing its schedule while keeping existing backups intact. Use it to clean up automated jobs without touching the user's own jobs.

Instructions

Delete a backup job Claude made (ID claude-…): its schedule goes, the backups it made stay. The user's own jobs cannot be deleted here.

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>",
      "id": "<id>",
      "reason": "<reason>"
    },
    "name": "delete_backup_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
hostYesThe host's id, from list_hosts.
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

A4.6/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, but the description adds the crucial nuance that only the schedule is removed while 'the backups it made stay.' That distinction (schedule vs. backup retention) cannot be derived from the annotations and directly affects whether an agent should proceed.

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?

Two short sentences, front-loaded with the action and scope, followed by the effect and the exclusion. No filler or restated metadata.

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 destructive mutation with annotations covering the safety profile and a schema that explains the approval-flow 'reason' parameter, this is nearly complete. It does not address behavior when the id is unknown or mismatched, a minor remaining gap.

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 67%: host and reason are described in the schema, but id is bare there. The description compensates by explaining the id's origin and format ('ID claude-…'), adding meaning the schema lacks.

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?

Names a specific verb and resource ('Delete a backup job') and immediately narrows scope to jobs 'Claude made (ID claude-…)', which lets an agent distinguish this from delete_backup (which removes backups) and from acting on user-owned jobs.

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?

Provides a clear negative case — 'The user's own jobs cannot be deleted here' — which tells the agent when not to call it. It stops short of naming a sibling that would handle user jobs, so the alternative path is left implicit.

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