Skip to main content
Glama

vspc_list_backup_policies

Read-onlyIdempotent

Lists Veeam Agent backup policies in VSPC to review OS, mode, creator, last change, and company/agent usage counts, with name filtering and pagination.

Instructions

Veeam Agent backup policies defined in VSPC: name, OS, mode, who created it, last change, and how many companies and agents use it.

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

Input Schema

NameRequiredDescriptionDefault
nameNoOnly items whose name contains this text (case-insensitive).
limitNoPage size (VSPC maximum 500).
offsetNoItems to skip (for the next page).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered. The description adds genuine behavioral value by revealing that results include usage counts across companies and agents, which implies aggregation cost, but it says nothing about paging behavior or result 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 with no filler; the field enumeration is compact and informative. It is a noun phrase rather than a verb-led statement, which slightly weakens the opening, but nothing is wasted.

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 simple read-only list tool with three fully documented optional parameters and no output schema, the description usefully enumerates the returned fields, which compensates for the missing output schema. Only the paging/aggregation behavior remains unexplained, a minor gap given the schema already documents limit and offset.

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 name substring filter, page size limits (VSPC max 500), and offset semantics are already documented in the schema. The description adds no additional meaning about how the name filter matches or how paging interacts with the usage counts, leaving it at the baseline.

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 names the concrete resource (Veeam Agent backup policies defined in VSPC) and enumerates the fields returned, so an agent knows exactly what entity is being listed. It does not explicitly contrast itself with siblings such as vspc_list_jobs or vspc_list_backup_servers, but the resource name is distinct enough to separate them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this tool versus alternatives, no prerequisites, and no exclusions. An agent must infer from the name and field list that this is the inventory view of agent backup policies, not a filtered or diagnostic query.

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