Skip to main content
Glama
Sign In
backrest-mcp

backrest-mcp

by TadMSTR
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_backup_freshness

Reports each backup plan’s last successful backup time and flags whether backups are stale, using plan schedules or a custom age threshold.

Instructions

Report, per plan, when it last backed up successfully and whether that is stale.

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": "get_backup_freshness"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_age_hoursNoMark a plan stale when its last good backup is older than this. When omitted, each plan's own schedule decides: 2x maxFrequencyHours, 2x maxFrequencyDays, or 26 hours for a cron schedule.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the core read-only reporting behavior and staleness concept, but does not explicitly state permissions, side-effect safety, rate limits, or other operational traits beyond what 'get' and 'report' imply.

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 a single front-loaded sentence with no wasted words. It efficiently communicates the reporting scope and the staleness check.

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?

With an output schema present, the description need not explain return values, and the schema fully documents the only parameter. The description is complete enough to understand the tool's purpose, though it lacks explicit usage guidance versus sibling tools.

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 description coverage is 100%, and the single optional parameter max_age_hours is fully documented in the schema, including its default schedule-based behavior. The description itself does not add parameter meaning beyond the word 'stale', so the baseline score of 3 is appropriate.

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 uses a specific verb and resource: report per plan the last successful backup and whether it is stale. It is clear what the tool does, though it does not explicitly distinguish itself from related siblings like get_health or get_summary.

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?

The description gives no explicit guidance on when to use this tool versus alternatives such as get_health, get_summary, or get_logs. It only implies the tool is for checking backup staleness, without exclusions or prerequisites.

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