Skip to main content
Glama

vspc_list_agent_jobs

Read-onlyIdempotent

List Veeam Agent jobs managed by VSPC to review computer, company, policy, latest result, last/next run, and failure messages; filter by company, name, or status and paginate results.

Instructions

Jobs of Veeam Agents (Windows, Linux, Mac) managed by VSPC, such as backup policies on workstations and servers: computer, company, policy, latest result, last run, next run, failure message.

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

Input Schema

NameRequiredDescriptionDefault
nameNoOnly items whose name contains this text (case-insensitive).
limitNoPage size (VSPC maximum 500).
offsetNoItems to skip (for the next page).
companyNoCompany (client) as its VSPC UID or its name (exact, or a unique part of it). Leave out for every company.
statusesNoOnly jobs whose latest session has one of these results.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive behavior, so the safety profile is fully covered. The description adds useful return-content context (computer, company, policy, latest result, last run, next run, failure message) and the platform scope, but says nothing about pagination defaults, total counts, or ordering.

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?

A single, front-loaded sentence that leads with the resource scope and then enumerates returned fields. It is compact and information-dense with no filler, though the field list is slightly list-like rather than structured.

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

Completeness3/5

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

For a zero-required-parameter list tool with no output schema, the description does well to name the returned fields and platform scope. It is incomplete on pagination behavior and result ordering, which matter for an agent paging through up to 500 items per request.

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%, with clear docs for name, limit, offset, company, and statuses, so the schema carries parameter meaning. The description adds no additional parameter semantics such as how name matching interacts with company filtering or the default page behavior; baseline 3 is appropriate.

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?

The description clearly identifies the resource: jobs of Veeam Agents (Windows, Linux, Mac) managed by VSPC, with examples of the record content. It implicitly distinguishes itself from the generic vspc_list_jobs by scoping to agent jobs, but it never names a sibling or explicitly contrasts its scope, so it stops short of full differentiation.

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?

Usage is implied by the scoped resource: use this to enumerate agent-managed jobs. However, there is no explicit when-to-use versus vspc_list_jobs, vspc_list_failed_jobs, or vspc_failed_jobs_summary, and no exclusion guidance, leaving the agent to infer the boundary between overlapping list tools.

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