Skip to main content
Glama

backup_history

Read-onlyIdempotent

Read recent Proxmox backup task metadata to review job outcomes and timing; this does not verify restore success.

Instructions

Read recent backup task metadata; this does not verify restore success.

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_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), so the bar is lower, and the description adds a genuinely non-obvious caveat: the metadata surface does not confirm restore success, which prevents a common misreading of results. It stops short of describing how 'recent' is bounded or whether the list is ordered/truncated by the limit.

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?

One sentence, front-loaded with the action and resource, with the caveat placed immediately after as a qualifier. No redundant wording or restatement of the tool name.

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?

For a zero-required-parameter, read-only listing tool with no output schema, the core intent is conveyed, and return-value detail is not required. Still missing are the recency window implied by 'recent' and the effect of the limit parameter, both of which materially affect interpretation of results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden for the single 'limit' parameter, yet it says nothing about it or about what 'recent' means in relation to it. An agent cannot tell from the text whether limit caps records, truncates silently, or bounds a time window.

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 description gives a specific verb and resource ('Read recent backup task metadata'), so an agent knows this returns backup task records rather than performing backups. It does not name or contrast with the sibling backup_jobs, so an agent cannot tell from the text alone how this differs from that adjacent tool.

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?

The clause 'this does not verify restore success' functions as an implicit when-not, steering agents away from using it as a restore-validation check. However, there is no positive guidance about the situations where this tool is the right choice, and no alternative tool is named for the restore-verification case.

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