Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Export Support Logs

export_support_logs

Collect Veeam support log bundles for selected jobs or hosts, optionally scoped to an ISO-8601 date range, for support case diagnostics.

Instructions

Collect a support log bundle (for a Veeam support case) for some jobs or hosts. With date_from/date_to (ISO-8601) only that range is exported, otherwise everything. Returns a log-export session.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "scope": "<scope>",
      "ids": "<ids>"
    },
    "name": "export_support_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes
scopeYes
date_toNo
date_fromNo
confirm_tokenNo
include_postgres_logsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the description needn't restate safety; it does add that the call creates a 'log-export session', which explains why a write-hinted, non-destructive operation is involved. However it never explains confirm_token (an apparent confirmation/authorization step), nor whether collection is long-running or how the session is later retrieved, which are exactly the behaviors an agent needs.

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?

Two compact sentences, front-loaded with the core action and followed by the date-range behavior. Nothing is wasted, though a single clause on confirm_token would have earned its place more than the return-session note.

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

Completeness3/5

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

An output schema exists, so the return value needn't be unpacked in detail. Still, for a 6-parameter, write-hinted tool with 0% schema coverage and an unexplained confirm_token flow, the description leaves meaningful gaps an agent must guess at.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden, and it covers only scope (jobs vs hosts), ids, and the date range semantics. Two parameters — confirm_token and include_postgres_logs — are left entirely unexplained, and their meaning is not inferable from names alone.

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 ('Collect a support log bundle ... for some jobs or hosts') and names the purpose (Veeam support case), which is far more informative than the title alone. It does not explicitly distinguish itself from the sibling export_configuration, so it falls short of a 5.

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?

It gives one useful conditional: with date_from/date_to only that range is exported, otherwise everything. There is no guidance on when to choose this over export_configuration, no prerequisites (support case, licensing, permissions), and no mention of when to set include_postgres_logs or confirm_token.

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