Skip to main content
Glama

pbs_job_create

Create a PBS scheduled job for sync, verify, or prune operations. Dry-run by default; use confirm=True to execute.

Instructions

MUTATION: create a PBS scheduled job. job_type = sync|verify|prune. Dry-run by default; confirm=True to execute and returns synchronously (no task UPID) — additive, no existing data affected. Needs PROXIMO_PBS_* config. To modify use pbs_job_update, to remove use pbs_job_delete, or to run it once immediately (bypassing the schedule) use pbs_job_run.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nsNoPBS namespace the job operates on; omit for the root namespace.
storeNoPBS datastore the job operates on.
job_idYesUnique ID for the new PBS scheduled job.
commentNoFree-text note stored on the job.
confirmNoGate: false returns a dry-run PLAN, true executes the creation.
job_typeYesPBS job type: sync | verify | prune.
scheduleNoProxmox calendar-event schedule string for the job.
proximo_targetNoWhich configured Proxmox target to run this call against — a target name from your multi-target config (a specific PVE/PBS/PMG/PDM box). Omit to use the single/default target from the environment; the selection applies only to this call.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description bears full burden. It discloses the tool is a mutation, dry-run by default, confirm=True triggers execution (returns synchronously, no task UPID), and is additive (no existing data affected). It also mentions config requirements. No contradictions or omissions of key behavioral traits.

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 description is extremely concise: two key sentences plus a clear list of alternatives. It front-loads the purpose and immediately provides the critical dry-run behavior. Every sentence adds value with no filler.

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?

Given the output schema exists (so return values need not be explained), the description covers purpose, mutability, default behavior, config dependency, and alternatives. It does not mention error handling or dry-run output format, but those are likely in the output schema. Still, a bit more context on dry-run output would be helpful.

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 baseline is 3. The description adds meaning for job_type ('sync|verify|prune') and confirms the dry-run/confirm gating. Other parameters (ns, store, schedule, etc.) are not elaborated beyond what the schema already provides, but the description adds moderate value.

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 starts with 'MUTATION: create a PBS scheduled job' and clearly specifies the verb (create) and resource (PBS scheduled job). It also distinguishes from sibling tools by naming alternatives: pbs_job_update, pbs_job_delete, and pbs_job_run, making it easy for an agent to select the correct tool.

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?

The description explains dry-run default and confirm=True for execution, states the config dependency (PROXIMO_PBS_*), and mentions alternatives for modification, removal, or immediate execution. However, it could explicitly state when not to use this tool (e.g., for immediate execution) but the alternatives cover that well.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/john-broadway/proximo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server