Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
VSPC_URLYesThe console address, https only, with its port: https://vspc.example.local:1280. A trailing /api/v3 is accepted.
LOG_LEVELNodebug, info (default), warn, error. Logs go to stderr. Tool arguments and the key are never logged.info
VSPC_API_KEYYesThe Simple REST API key. Never logged; removed from every error message.
VSPC_ACCEPT_SELF_SIGNEDNotrue only when the console's certificate is self-signed or not issued for the name in VSPC_URL. The connection stays encrypted, but the server is not authenticated, so use this only over a trusted path (VPN). Default false.false

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}
logging
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
vspc_aboutA

Veeam Service Provider Console version and installation details (server version, current Veeam Agent and management agent versions). A cheap first call to check the connection and key.

vspc_list_companiesA

Companies (clients) managed in VSPC, sorted by name: UID, name, status. Use a UID or name from here as company in the other tools.

vspc_get_companyA

One company: status, reseller, subscription plan, services enabled for it (owner credentials are never returned).

vspc_list_backup_serversB

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

vspc_list_jobsA

Jobs on managed Veeam Backup & Replication servers (VM backup, replication, backup copy, tape, file share, agent jobs managed by VBR): latest result, last run and end, duration, destination, failure message. Filter by company, backup server, latest result and name. For "what failed recently" across all clients, use vspc_list_failed_jobs or vspc_failed_jobs_summary.

vspc_list_agent_jobsB

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.

vspc_list_failed_jobsA

Every job across ALL companies whose latest session failed (or ended with a warning) in the last N hours, newest first, with company, backup server or computer, and the failure reason. Covers Veeam Backup & Replication server jobs, Veeam Agent jobs and Veeam Backup for Microsoft 365 jobs in one call. VSPC keeps only the latest session of each job, so a job that failed and then succeeded on retry is not listed. For one row per job with retries folded together, use vspc_failed_jobs_summary.

vspc_failed_jobs_summaryA

Summary of backup failures across ALL companies in the last N hours: one row per job (retries of the same job, and one agent job failing on several computers of a company, are folded together, worst result first), counts per company, and VSPC's session counts (successful, warning, failed sessions) for the window. The best first call for "which backups failed in the last 24 hours?".

vspc_list_alarmsA

Triggered (active) VSPC alarms across every client, newest first: alarm name, status (Error, Warning, ...), time, message, the object (job, server, agent, repository...), computer and company. Defaults to Error and Warning alarms.

vspc_list_protected_vmsA

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).

vspc_list_backup_policiesB

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

vspc_get_license_usageA

Current license usage by organization and server (Veeam Backup & Replication, Cloud Connect, VB365, VSPC, Veeam ONE): per workload type the used, new and rental units and counts, plus totals per workload across the result. Optionally one company.

vspc_get_console_licenseB

The VSPC console license: edition, package, status, expiry and support expiry, last update result.

vspc_start_jobA

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.

vspc_retry_jobA

Retries a failed job on a managed Veeam Backup & Replication server (only the failed objects are processed again). VSPC queues the retry and returns at once.

vspc_acknowledge_alarmA

Acknowledges a triggered VSPC alarm (alarm UID from vspc_list_alarms) with a comment. The alarm stays until it is resolved.

vspc_resolve_alarmA

Marks a triggered VSPC alarm as resolved, with a comment. If the cause is still there, VSPC triggers it again.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 17 tools

Disambiguation4/5

Tools map cleanly to distinct resources (companies, backup servers, VBR jobs, agent jobs, alarms, licenses, protected VMs, policies), and the descriptions actively disambiguate the trickiest pairs (vspc_list_jobs vs vspc_list_failed_jobs vs vspc_failed_jobs_summary) with explicit "use X instead" guidance. The only residual overlap is between list_jobs/list_failed_jobs/failed_jobs_summary, which is an intentional layering but still requires the agent to read descriptions carefully.

Naming Consistency4/5

Almost everything follows vspc_<verb>_<noun> in snake_case (list_companies, get_company, start_job, retry_job, resolve_alarm). Two deviations stand out: vspc_failed_jobs_summary uses a noun-only lead instead of a verb, and vspc_about is a bare verbless noun, breaking the otherwise predictable pattern.

Tool Count4/5

17 tools is on the heavier side of the ideal band, but each maps to a real object in an enterprise backup console (companies, servers, jobs, agents, alarms, licensing, VMs, policies), so most earn their place. A couple of the read variants (console license vs license usage, failed jobs vs summary) could arguably be merged or made flag-based.

Completeness3/5

Read coverage is strong, and the action surface (start/retry job, acknowledge/resolve alarm) covers the core triage workflow. However, there is no stop/cancel job, no session-history or per-job detail tool, no repository/agent inventory, and no create/update for policies or companies, leaving obvious dead ends such as 'a job is stuck and I can't stop it.'

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues