Skip to main content
Glama

Simulate a job schedule

proxmox_simulate_schedule
Read-only

Preview the next run times for a Proxmox calendar-event schedule, such as backups or replication jobs, to verify it before saving.

Instructions

Show the next run times of a Proxmox calendar-event schedule (as used by backup, replication and other jobs), e.g. 'mon..fri 02:00' or '*/15'. Useful to check a schedule before saving it.

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": {
      "schedule": "<schedule>"
    },
    "name": "proxmox_simulate_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
scheduleYesCalendar event, e.g. 'daily', 'sat 03:30', '*/2:00'
starttimeNoStart from this UNIX time instead of now
iterationsNoHow many run times to show (default 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false; the description adds the key behavioral fact that this computes future run times rather than persisting anything, reinforcing the non-mutating nature. It also hints at the return content ('next run times'), which matters because there is no output schema. It does not say what happens on an invalid schedule expression, which is the main remaining gap.

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 tight sentences with the core function front-loaded and the motivating use case second; no filler or restatement of the title.

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 three-parameter read-only computation with full schema coverage and no output schema, the description covers what it does, why you would call it, and roughly what comes back. Only the failure behavior for malformed schedules and the exact shape of the returned times are left unspecified.

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 coverage is 100%, so all three parameters are already documented with examples and defaults, making the baseline 3. The description's inline examples ('mon..fri 02:00', '*/15') add the range and step syntaxes, a marginal gain since the schema already supplies its own examples, and starttime/iterations are not discussed at all.

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?

States a specific verb ('show the next run times') and a specific resource ('Proxmox calendar-event schedule'), with the scope spelled out as the format used by backup, replication and other jobs. It is clearly a dry-run calculator rather than a job-configuration fetch, so it is distinguishable from the get_* siblings without opening any 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?

'Useful to check a schedule before saving it' gives a concrete usage context and implies the counterpart action (validating prior to persisting). There are no explicit exclusions or named alternatives, but the intended moment of use is unambiguous.

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