Skip to main content
Glama

vspc_start_job

Starts a Veeam Backup & Replication job on a managed server immediately using its job UID; VSPC queues the run and returns, so check status later with vspc_list_jobs.

Instructions

Starts a job on a managed Veeam Backup & Replication server now (job UID from vspc_list_jobs or vspc_list_failed_jobs). VSPC queues the start and returns at once; check the result later with vspc_list_jobs.

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_start_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

A4.1/5.0
Behavior4/5

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

Adds behavior the annotations cannot express: the start is queued asynchronously and the call returns immediately, so the agent knows not to poll for a completed result. Remaining gaps are edge behavior — what happens if the job is already running or the UID is invalid — none of which is disclosed.

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 sentences, zero filler. The async caveat is placed after the action description where it is needed, and the pointer to the listing tools is folded into the parenthetical rather than padding the prose.

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 mutation with no output schema, the description covers what an agent needs: how to obtain the UID, that the call is fire-and-forget, and how to verify the outcome. It stops short of stating the failure mode or the impact of starting an already-running job.

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

Parameters4/5

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

Schema coverage is 100% and documents job_uid, but the description adds real value by identifying which tools produce a valid UID (vspc_list_jobs, vspc_list_failed_jobs) and noting it is the VSPC instanceUid. That provenance goes beyond the schema text.

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?

Specific verb+resource: 'Starts a job on a managed Veeam Backup & Replication server now', with the UID source named. It does not explicitly distinguish itself from the closest sibling vspc_retry_job, so the agent must infer 'start a new run' vs 'retry a failed run' from names alone.

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 clear operating context: the UID comes from vspc_list_jobs or vspc_list_failed_jobs, and the follow-up check goes to vspc_list_jobs. No exclusion guidance for related actions such as retry, and no preconditions (job must be idle, permissions) are stated.

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