Skip to main content
Glama
AIops-tools

Veeam AIops

by AIops-tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

restore_list_points

Read-only

Lists Veeam restore points newest first, with optional backup ID filtering and a limit, to inspect available recovery points.

Instructions

[READ] The newest restore points (id, name, creationTime, type), newest first.

Returns {"restorePoints": [...], "returned", "limit", "truncated", "order"}. truncated=true means older points exist beyond this window — raise limit or filter by backup_id; do not read a short list as "that is all there is". With backup_id, a server that ignores the filter is refused, not trusted.

Args: backup_id: Optional Veeam backup id (see backup_list) to filter by. limit: Points to return, 1-1000 (default 100). target: Veeam target name from config; omit to use the default.

Input Schema

NameRequiredDescriptionDefault
limitNo
targetNo
backup_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.13.1
    • addedInput schema / properties / limit
      Added value: +{
+  "default": 100,
+  "title": "Limit",
+  "type": "integer"
+}
  2. Addedv0.10.0
  3. Removedv0.8.0
  4. First observedv0.2.0

TDQS

A4.3/5.0
Behavior5/5

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

With readOnlyHint already covering safety, the description adds substantial non-obvious behavior: the exact return envelope, truncation semantics ('do not read a short list as that is all there is'), and a filter-integrity guarantee ('a server that ignores the filter is refused, not trusted'). This is context an agent cannot get from annotations.

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?

Front-loads the resource and ordering, then the return shape, then the critical truncation warning, then args. Every block earns its place; the enabled-by-default output envelope is justified by the absence of an output schema.

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, the description supplies the return shape and truncation semantics itself, and it fully documents the three undocumented parameters including default target behavior. 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% (only titles/defaults), so the description carries the load and documents all three: backup_id purpose and source, limit range 1-1000 with default, and target as a named config with a default fallback. The 1-1000 bound is not in the schema at all.

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?

States a specific verb+resource (list newest restore points) and enumerates the returned fields (id, name, creationTime, type) plus ordering. It does not explicitly contrast itself with a sibling restore tool, but none exists in the sibling list, so an agent can identify it easily.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit operating guidance: when truncated=true, raise limit or filter by backup_id; and it points to backup_list for obtaining backup ids. It lacks an explicit when-to-use vs. a named alternative, but there is no competing restore-point tool.

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