Skip to main content
Glama

backup_jobs

Read-onlyIdempotent

Retrieve selected backup scheduling metadata to inspect configured schedules and verify backup configuration in a Proxmox environment.

Instructions

Read selected backup scheduling metadata.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "backup_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds that the payload is 'scheduling metadata', implying configuration rather than execution history, which is mild but real added context. It says nothing about scope, size, or the meaning of 'selected', which is the one behavior an agent most needs clarified.

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?

One short sentence with no waste, but it is under-specified rather than concise — the single word 'selected' carries unexplained meaning and the whole definition is front-loaded with ambiguity instead of a scoping statement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no parameters and no output schema, the description is the only source of information about what comes back, and it does not say what a job record contains or what 'selected' ranges over. For a tool sitting next to backup_history, the missing differentiation and result-shape hint leave the agent under-informed.

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?

The tool takes no parameters, so per the baseline there is little for the description to document. The only wrinkle is the word 'selected', which implies a filter that does not exist in the schema — a minor inconsistency but not enough to penalize heavily.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'Read' and the object 'backup scheduling metadata' give a rough idea, but 'selected' is unexplained and there is no inkling of how jobs are selected — the tool takes zero parameters, so the qualifier is opaque. It also does not distinguish itself from the sibling backup_history, which an agent could easily confuse with scheduling metadata.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance, no exclusions, no mention of backup_history as the alternative for past run records versus scheduled configuration. The agent is left to guess which of the two backup tools to call.

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