Skip to main content
Glama
AIops-tools

Veeam AIops

by AIops-tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

session_list

Read-only

List Veeam backup sessions with ID, name, type, state, and result, ordered by recency; set limit or target as needed.

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

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.7/5.0
Behavior4/5

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

Annotations only supply readOnlyHint=true; the description goes further by documenting the return envelope keys, the ordering guarantee, and the meaning of truncated=true. This is real behavioral context that the annotation cannot carry, though it says nothing about auth, rate limits, or target-resolution failures.

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 a [READ] tag, then return shape, then args, in three tight blocks with no filler. Minor redundancy in 'newest sessions ... newest first' keeps it just short of ideal.

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?

For a two-parameter read-only list with no output schema, the description supplies the return keys, truncation semantics, ordering, and parameter bounds — everything an agent needs to call and interpret it correctly.

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 carries the full burden and largely does: limit is bounded (1-1000, default 100) and target's origin and default behavior are explained. Both parameters get meaning beyond the bare integer/string types in the schema.

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 and resource ('the newest sessions') plus the fields returned and the ordering ('newest first'), which separates it from single-session tools like session_get or session_log. It doesn't explicitly name a sibling, but the list scope is unambiguous.

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?

No when-to-use or when-not-to-use guidance. The agent is not told to reach for session_get to inspect one session or session_log for logs, nor is any filtering/precondition context given. Usage is only implied by the list-shaped description.

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