Skip to main content
Glama
claude-proxmox-controller

claude-proxmox-controller

list_backup_jobs

Read-onlyIdempotent

List scheduled Proxmox backup jobs, identify guests not covered by any job, and distinguish Claude-created jobs from user-managed ones.

Instructions

The scheduled backups (Datacenter → Backup) and the guests no job covers. by_claude: a job Claude made (its ID begins with claude-) — only those can Claude change or delete; the user's jobs only the user changes, in the app.

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>"
    },
    "name": "list_backup_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYesThe host's id, from list_hosts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare a safe, idempotent, closed-world read, so the description's added value is the ownership model: jobs whose ID begins with 'claude-' are the only ones Claude may change or delete, and user-created jobs must be modified in the app. That is genuine behavioral context an agent cannot get from the annotations, though the coverage/return-shape side is left vague.

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

Conciseness3/5

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

The first sentence front-loads the resource well, but the second is a fragment ('by_claude: ...') that reads like a field doc pasted into the description and mixes output-field semantics with permission rules. Nothing is redundant, but the structure is awkward and costs clarity.

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?

With no output schema, the description should explain the returned shape; it does partially (jobs plus uncovered guests, plus a by_claude indicator) but never clarifies whether by_claude is a field, how uncovered guests are represented, or how the two result sets are combined. Adequate for a read-only list, but a meaningful gap remains for an agent parsing the response.

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?

The single parameter is fully documented in the schema (host id, sourced from list_hosts), so the schema carries the burden. The description adds no syntax, format, or scope detail about host beyond what the schema already says; it only implies results are host-scoped, which is already evident.

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 first sentence names a specific resource (scheduled backup jobs, located at Datacenter → Backup) and an unusual secondary output (guests not covered by any job), which is enough to separate it from list_backups and list_guests. The phrasing is telegraphic rather than a clean verb+resource statement, and no sibling is named explicitly, so it stops short of a 5.

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?

There is no explicit 'use this when' clause or named alternative, so the agent must infer that this is the discovery step before edit_backup_job/delete_backup_job. The ownership note does implicitly route behavior (only claude- jobs are actionable for Claude), which is useful but indirect guidance rather than stated usage rules.

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