Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Import Configuration

import_configuration
Destructive

Load configuration objects exported from another VBR server, update existing items, and return an automation session to stop afterward.

Instructions

Import configuration objects (as produced by export_configuration, e.g. on another VBR server). Objects that exist already may be updated. Returns an automation session; stop it with stop_automation_session. Confirmed by the server.

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": {
      "kind": "<kind>",
      "collection": "<collection>"
    },
    "name": "import_configuration"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
collectionYesThe import collection - exactly the structure `export_configuration` returns, e.g. {'jobs': [...]}, {'proxies': [...]}, {'viHosts': [...], 'windowsHosts': [...]} for managed servers, {'LinuxHardenedRepositories': [...], ...} for repositories. See describe_endpoint.
confirm_tokenNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructive=true and non-idempotent, and the description adds real value on top: that existing objects are updated rather than skipped, that the call is asynchronous and returns an automation session that must be stopped, and that the server confirms the operation. It stops short of saying what exactly is overwritten or what permissions/validation failures are possible for a destructive import.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, each carrying distinct information (purpose, update semantics, session lifecycle, confirmation) with no repetition of the schema or annotations. The purpose is front-loaded and the follow-up action is attached to the sentence that introduces the session.

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?

Return values are covered by the output schema and the safety profile by annotations, and the description fills the remaining gaps on side effects and async lifecycle. The main residual hole is the confirmation/token behavior for a destructive import, which an agent would likely need before calling.

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

Parameters3/5

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

Schema coverage is only 33% and nested, so the description is expected to carry weight; it does explain that `collection` must match the exact structure `export_configuration` returns and references 'describe_endpoint' via the schema for per-kind shapes. However, `confirm_token` is never mentioned in the description, and the cryptic 'Confirmed by the server' does not explain the confirmation workflow implied by that parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Import configuration objects') and immediately anchors the input to a sibling tool ('as produced by `export_configuration`'), which separates it cleanly from export_configuration and the generic write tools. An agent can tell what this does without opening the schema.

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 a concrete usage scenario ('e.g. on another VBR server') and describes the effect on pre-existing objects ('may be updated'), which tells the agent when this is the right call. It also names the required follow-up (`stop_automation_session`), but it never states when NOT to use it or which sibling to prefer for partial/incremental changes.

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