Skip to main content
Glama
Sign In
Veeam AIops

Veeam AIops

by AIops-tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

proxy_list

Read-only

List Veeam backup proxies with their IDs, names, types, and servers. Specify a configured Veeam target or omit it to use the default.

Instructions

[READ] List backup proxies (id, name, type, server).

Args: target: Veeam target name from config; omit to use the default.

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": "proxy_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior3/5

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

The '[READ]' tag duplicates the readOnlyHint annotation rather than extending it, and the description otherwise adds only the default-target behavior. With annotations already declaring the safety profile for a simple list operation, 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?

Tight and front-loaded: one sentence for purpose plus a one-line arg note. The only waste is the redundant '[READ]' marker already supplied by annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, listing the returned fields (id, name, type, server) is exactly the right compensation for a single-parameter, read-only listing tool. Nothing needed to call it correctly 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 coverage is 0% and the only parameter has a bare 'Target' title, so the description carries the burden. It does explain the semantics well: the value is a Veeam target name from config and omitting it selects the default, which meaningfully exceeds the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List backup proxies') and enumerates the returned fields (id, name, type, server). This is enough to distinguish it from sibling listings such as repository_list or managed_server_list without opening any schema.

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 only implied: it is a read-only enumeration of proxies. There is no explicit statement of when to prefer this over siblings like managed_server_list or repository_list, though the guidance on omitting 'target' to fall back to the default is useful.

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

Deploy Server

Other Tools