Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Send Test Email

send_test_email

Sends a test email using the configured email notification settings to verify that Veeam Backup & Replication email alerts are working.

Instructions

Send a test message with the configured email notification settings (update_settings(area='email')).

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

Input Schema

NameRequiredDescriptionDefault
confirm_tokenNo

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 it is a non-destructive, non-read-only, non-open-world operation, so the safety profile is covered. The description adds that delivery relies on already-stored configuration rather than per-call recipients, but says nothing about whether the token parameter gates execution or what a failed send looks like — notable given openWorldHint=false on something that dispatches a message.

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?

One short sentence, front-loaded with the action and immediately qualified by the configuration source. Nothing is wasted, though the sentence carries no information about the parameter.

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?

Output schema exists, so return values need no explanation, and the tool is conceptually simple. The remaining gap is the undocumented confirm_token and the absence of any statement about delivery outcome or failure modes, which leaves the definition adequate but incomplete.

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% and the single parameter `confirm_token` (nullable, default null) is never mentioned in the description. For an optional confirmation token on a send action, an agent needs to know whether it is required for real dispatch or is a safety interlock; the description provides no such meaning.

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 ('Send a test message') and scopes it to the configured email notification settings, which separates it from generic mail or settings tools. It does not explicitly contrast with a sibling, but the purpose 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 Guidelines3/5

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

The parenthetical reference to `update_settings(area='email')` implies the prerequisite that email settings should be configured first, which is genuinely useful routing. There is no explicit statement of when not to use it, what to do on delivery failure, or how it relates to other diagnostics tools.

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