Skip to main content
Glama

vspc_get_license_usage

Read-onlyIdempotent

Retrieve current Veeam license usage by organization and server, including used, new, and rental units and counts per workload type, with optional company and product filters.

Instructions

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.

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

Input Schema

NameRequiredDescriptionDefault
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.
server_typeNoOnly usage on servers of this product.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/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 covered. The description adds genuine context beyond that by specifying the aggregation granularity of the response: per-workload-type used/new/rental units and counts, plus totals per workload across the whole result set. It still says nothing about data freshness ('current' is undefined) or the cost of open-world queries.

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?

The resource and scope are front-loaded in the first clause, and the product list in parentheses is a compact enumeration rather than padding. The single dense sentence with nested parentheses is slightly hard to parse but wastes no words.

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, four-parameter reporting tool with no output schema, the description covers what is measured, at what granularity, and that totals are included, which is enough for an agent to call it correctly. The remaining gap is that it never explains the semantics of 'new' vs 'used' vs 'rental' units or how pagination interacts with the reported totals.

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 limit, offset, company and server_type are already documented in the schema, and the baseline is 3. The description reinforces the company filter ('Optionally one company') and the server dimension, but adds no syntax, matching rules, or defaults beyond what the schema states.

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 states a specific verb and resource ('Current license usage by organization and server') and enumerates the covered products and the exact breakdown returned (used, new, rental units and counts, plus totals per workload). It does not name a sibling such as vspc_get_console_license, so the agent must infer the distinction between product license usage and console licensing.

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 when-to-use guidance, no statement of when to prefer this over vspc_get_console_license or vspc_list_companies, and no exclusions or prerequisites. 'Optionally one company' describes a filter's effect rather than a usage condition, so the agent gets only an implied sense of purpose from the noun phrase.

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