Skip to main content
Glama

vspc_failed_jobs_summary

Read-onlyIdempotent

Summarizes backup failures across all companies for a chosen look-back window, folding retries into one row and showing per-company and session counts to identify failed backups quickly.

Instructions

Summary of backup failures across ALL companies in the last N hours: one row per job (retries of the same job, and one agent job failing on several computers of a company, are folded together, worst result first), counts per company, and VSPC's session counts (successful, warning, failed sessions) for the window. The best first call for "which backups failed in the last 24 hours?".

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

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.
include_warningsNoAlso include jobs whose latest session ended with a warning.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and open-world, so the description's value is in disclosing aggregation behavior: retries of the same job and one agent job failing on several computers are folded together, with worst result first. That is non-obvious semantics an agent could not infer from the schema. It does not mention row caps, pagination, or the window's time basis, which are the remaining behavioral unknowns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core scope, then the output shape, then a one-line usage hint. The parenthetical folding explanation is dense but earns its place by preventing double-counting mistakes. Slightly long as a single sentence, but there is 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?

With no output schema, the description carries the return-value burden and does so by naming the three result components and the row ordering. For a read-only aggregation tool with fully documented params this is nearly sufficient; only limits on result size and the time window's reference point are unaddressed.

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%, so the schema already documents hours, company, and include_warnings with defaults and bounds. The description reinforces the default scope ('across ALL companies', 'last N hours') but adds no format or edge-case detail for any individual parameter. Baseline 3 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?

States a specific resource and scope: 'Summary of backup failures across ALL companies in the last N hours', and then enumerates exactly what the output contains (per-job rows, per-company counts, VSPC session counts). This distinguishes it from the list-style siblings such as vspc_list_failed_jobs without needing to name them.

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?

Gives an explicit usage cue: 'The best first call for "which backups failed in the last 24 hours?"', which tells the agent to reach for this before detail tools. It does not state when to prefer the sibling list tools or what to do after (e.g., retry via vspc_retry_job), so the routing guidance stops short of full when/when-not coverage.

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