Skip to main content
Glama

vspc_list_failed_jobs

Read-onlyIdempotent

List failed or warning backup jobs across all companies within a chosen lookback window, including company, server or computer, and failure reason.

Instructions

Every job across ALL companies whose latest session failed (or ended with a warning) in the last N hours, newest first, with company, backup server or computer, and the failure reason. Covers Veeam Backup & Replication server jobs, Veeam Agent jobs and Veeam Backup for Microsoft 365 jobs in one call. VSPC keeps only the latest session of each job, so a job that failed and then succeeded on retry is not listed. For one row per job with retries folded together, use vspc_failed_jobs_summary.

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

Input Schema

NameRequiredDescriptionDefault
hoursNoLook-back window in hours (default 24).
companyNoCompany (client) as its VSPC UID or its name (exact, or a unique part of it). Leave out for every company.
sourcesNoJob kinds: backup_server (VBR jobs), agent (Veeam Agent jobs), vb365 (Microsoft 365 jobs). Default all.
max_rowsNoMost rows returned (newest first); `count` is always the full number.
statusesNoResults to include: ["Failed"] (default) or ["Failed","Warning"].
backup_server_uidNoOnly jobs on this Veeam Backup & Replication server (then agent and VB365 jobs are skipped).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, and the description still adds real substance: session-retention semantics ('VSPC keeps only the latest session'), retry behavior, newest-first ordering, and that this is a cross-product aggregation in one call. These are behavioral traits no annotation conveys.

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?

Three sentences, front-loaded with the scope and ordering, then the coverage statement, then the alternative-routing hint. Every sentence carries distinct information with no restatement of the name or filler.

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

Completeness5/5

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

For a six-parameter, no-required-parameter read tool with no output schema, the description covers scope, ordering, returned fields, retention caveat and the default company spread. Combined with full schema coverage and safety annotations, an agent has everything needed to call it correctly.

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 every parameter is already documented, including hours, company, sources, statuses and max_rows defaults. The description reinforces a few of these (all companies by default, the three job kinds, latest-session semantics) but adds little syntax or edge-case detail beyond the schema, so the baseline applies.

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?

Specific verb and resource: lists failed/warning jobs across ALL companies in the last N hours, newest first. It names the fields returned (company, backup server or computer, failure reason) and explicitly scopes the three covered job families (VBR, Agent, VB365), which separates it from single-source siblings like vspc_list_agent_jobs.

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

Usage Guidelines5/5

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

Explicitly routes the agent to a named alternative: use vspc_failed_jobs_summary when one row per job with retries folded together is wanted. It also states a key when-not condition — a job that failed then succeeded on retry will not appear — so the agent knows this is latest-session-only reporting.

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