Skip to main content
Glama

vspc_list_backup_servers

Read-onlyIdempotent

Lists Veeam backup servers managed by VSPC across all clients, showing name, company, version, role, and health status. Filter by name, company, or status to find inaccessible or warning servers.

Instructions

Veeam Backup & Replication servers managed by VSPC, across every client: name, company, version (with patch), role, and status (Healthy, Warning, Inaccessible).

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

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 servers with one of these statuses, e.g. ["Inaccessible","Warning"].

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, idempotentHint, non-destructive, and open-world, so the safety profile is covered. The description adds useful scope context ('across every client') and enumerates possible status values, but says nothing about ordering, pagination behavior, or what an empty result means. With annotations doing the heavy lifting, this is adequate but not rich.

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 dense sentence with the resource front-loaded and the return fields listed afterward. There is no wasted wording, though it is a noun fragment rather than a full statement of action.

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?

This is a read-only list tool with a fully described five-parameter schema and complete annotations; the description also enumerates returned fields, which compensates for the missing output schema. Only the absence of any result-ordering or pagination context keeps it from being fully complete.

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 every parameter (name, limit, offset, company, statuses) is already documented in the schema. The description's mention of the status values and 'across every client' loosely mirrors the statuses and company parameters but adds no syntax or semantics beyond the schema, so 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?

The description names a specific resource (Veeam Backup & Replication servers managed by VSPC) and enumerates the fields returned, so an agent knows precisely what comes back. It lacks an explicit verb and doesn't distinguish itself from siblings like vspc_list_companies or vspc_list_agent_jobs, but the resource is specific enough to disambiguate.

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?

No when-to-use guidance is given: there is no statement of alternatives, prerequisites, or the situations in which listing backup servers is the right call versus listing jobs, alarms, or companies. The phrase 'across every client' hints at scope but is not framed as usage guidance.

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