Skip to main content
Glama

vspc_list_protected_vms

Read-onlyIdempotent

Lists protected virtual machines managed by Veeam Backup & Replication, including company, backup server, restore point details, and immutability. Sort by oldest restore point to find stale backups.

Instructions

Virtual machines protected by managed Veeam Backup & Replication servers: VM, company, backup server, restore points, latest restore point date, sizes, immutability. oldest_first: true puts the VMs with the oldest latest restore point first (stale backups).

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

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.
oldest_firstNoSort by latest restore point date, oldest first.

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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds value by enumerating the concrete data returned per VM, which matters because there is no output schema, and by giving the business meaning of the sort order rather than leaving it as a bare flag.

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?

Two sentences with no filler: the first front-loads what the tool lists and what each row contains, the second covers the one non-obvious parameter. The field enumeration is dense but each field earns its place given no output schema exists.

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 read-only list tool with 5 fully documented parameters and no output schema, the description supplies the return-value shape and the one semantic flag, which is close to complete. It does not address pagination behavior or ordering defaults beyond the schema, but nothing essential for correct invocation is missing.

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 description coverage is 100%, so baseline is 3; the description earns an extra point for explaining the intent behind `oldest_first` (identifying stale backups), which goes beyond the schema's mechanical 'sort by latest restore point date, oldest first'. Other parameters (name, limit, offset, company) are left entirely to the schema, which is acceptable given full coverage.

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?

Names a specific resource and verb-equivalent: virtual machines protected by managed Veeam Backup & Replication servers, plus the per-item fields returned (VM, company, backup server, restore points, sizes, immutability). It is readily distinguishable from siblings like vspc_list_backup_servers or vspc_list_companies, though it does not name any sibling explicitly.

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 rather than stated: the description explains that `oldest_first: true` surfaces VMs with the oldest latest restore point (stale backups), which hints at the stale-backup auditing scenario. There is no explicit when-to-use/when-not guidance or reference to an alternative tool for related queries.

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