Skip to main content
Glama

vspc_retry_job

Retry a failed Veeam Backup & Replication job so only failed objects are processed again; the retry is queued and returns immediately.

Instructions

Retries a failed job on a managed Veeam Backup & Replication server (only the failed objects are processed again). VSPC queues the retry and returns at once.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "job_uid": "<job_uid>"
    },
    "name": "vspc_retry_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_uidYesJob UID (VSPC instanceUid of the job).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, open-world action, but the description adds genuinely new behavior: the retry is asynchronous ('VSPC queues the retry and returns at once'), so no completion result is returned, and only failed objects are reprocessed. That async caveat is exactly the kind of context annotations cannot convey.

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?

Two tight sentences, front-loaded with the action and scope, then the execution semantics. Nothing is redundant and every clause carries information.

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?

For a single-parameter action with no output schema, the definition covers the key facts an agent needs: what it acts on, what gets reprocessed, and that it returns immediately without waiting for completion. It stops short of stating permission requirements or behavior when the job is not failed, but the essentials are present.

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?

There is exactly one parameter and the schema documents it fully at 100% coverage (job_uid, uuid, VSPC instanceUid of the job). The description adds no format or sourcing detail beyond that, so the schema carries the parameter burden and the baseline of 3 applies.

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?

States a specific verb (retry) and resource (a failed job on a managed VBR server), plus the scope qualifier that only failed objects are reprocessed. This implicitly distinguishes it from vspc_start_job, but no sibling is named, so differentiation is inferential rather than explicit.

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 word 'failed' and the note that only failed objects are processed imply this tool is for jobs already in a failed state, which is useful guidance. However, it never states what to do otherwise (e.g., use vspc_start_job for a non-failed job) or what happens if the job is not failed, leaving the when-not condition unstated.

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