Skip to main content
Glama
AIops-tools

Veeam AIops

by AIops-tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

job_failure_rca

Flag and triage failed backup sessions by analyzing logs to identify likely causes like repository full, source unreachable, or VSS failure, prioritized worst-first.

Instructions

[READ] Triage recent backup-job sessions: flag every Failed/Warning run.

Pulls the newest limit sessions, fetches the failing log records for each bad run, and categorizes the likely cause (repository full, source/guest unreachable, credential/VSS failure, retry exhaustion) worst-first, citing the session result and the matched error substring for every finding. sessionsTruncated=true means older sessions were not analysed. For "what failed last night", pass since_hours=24 so the window is a time span rather than whatever fits in the newest limit sessions of every type.

Args: limit: Newest sessions to analyse, 1-1000 (default 100). since_hours: Only sessions created in the last N hours (optional). target: Veeam target name from config; omit to use the default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
targetNo
since_hoursNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.13.1
    • addedInput schema / properties / limit
      Added value: +{
+  "default": 100,
+  "title": "Limit",
+  "type": "integer"
+}
    • addedInput schema / properties / since_hours
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Since Hours"
+}
  2. Addedv0.10.0

TDQS

A4.6/5.0
Behavior4/5

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

No annotations, so the description carries the full burden and does so well: it declares the [READ] nature, explains the two-stage fetch-then-categorize behavior, names the cause taxonomy, and discloses the sessionsTruncated return flag signaling incomplete analysis. Missing only auth/permission context.

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?

Front-loads the core verb and scope in the first line, then the derived behavior and the sessionsTruncated caveat, then a compact Args block. Every sentence earns its place with no 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?

With no output schema, the description still explains what comes back (findings citing session result and matched error substring, and the sessionsTruncated flag). Nothing an agent needs to call this correctly is missing.

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

Parameters5/5

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

Schema description coverage is 0%, so the description fully compensates: limit is 'newest sessions to analyse, 1-1000 (default 100)', since_hours is 'only sessions created in the last N hours', and target is 'Veeam target name from config; omit to use the default'. Each parameter gains meaning beyond the bare schema.

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 verb+resource (triage backup-job sessions, flag Failed/Warning runs) and its output shape (categorized causes, worst-first, with cited session result and error substring). An agent can distinguish it from job_list or session_list, which merely enumerate.

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 rule: 'For "what failed last night", pass since_hours=24 so the window is a time span rather than whatever fits in the newest limit sessions.' It does not name sibling alternatives to use instead, so it stops short of a 5.

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