Skip to main content
Glama
AIops-tools

Veeam AIops

by AIops-tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

session_list

List the newest Veeam backup sessions with details like state and result, and see if older sessions exist beyond the returned window.

Instructions

[READ] The newest sessions with id, name, type, state, result, newest first.

Returns {"sessions": [...], "returned", "limit", "truncated", "order"}. truncated=true means older sessions exist beyond this window.

Args: limit: Sessions to return, 1-1000 (default 100). target: Veeam target name from config; omit to use the default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
targetNo

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

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does disclose meaningful traits: the [READ] marker, the exact response shape, newest-first ordering, and the semantics of truncated=true. It does not cover permissions, rate limits, or how to page past the truncation window, so it stops short of complete behavioral disclosure.

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-loaded with the read marker and purpose, then return shape, then args as a compact list; every line adds information. The field enumeration line is slightly dense but is not wasted space.

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?

With no output schema and no annotations, the description supplies the return keys, ordering, and truncation semantics, which is most of what an agent needs. It omits how to retrieve sessions beyond the truncation window (there is no offset parameter) and what happens on an unknown target.

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%, so the description must compensate, and it does: the limit range (1-1000) and default (100) are supplied beyond the bare schema default, and target is explained as a config-defined Veeam target that defaults when omitted. Only the fallback target name and any invalid-target behavior remain unstated.

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 resource (sessions) with the returned fields and the ordering rule ('newest first'), so an agent knows exactly what comes back. It does not explicitly contrast itself with siblings like session_get or session_log, leaving the boundary to inference.

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: this is the enumeration entry point versus session_get (single session) and session_log (log detail), but neither alternative nor a when-not-to-use condition is named. The 'omit to use the default' note on target is the only concrete guidance given.

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