Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Create Object

create_object

Create a Veeam Backup & Replication object from a complete POST spec for the selected kind, including jobs, repositories, servers, and credentials.

Instructions

Create a VBR object from a full spec (the POST body of its collection).

Kinds: job, managed_server, repository, scale_out_repository, proxy, mount_server, credentials, cloud_credentials, encryption_password, kms_server, protection_group, recovery_token, unstructured_data_server, entra_id_tenant, ad_domain, global_vm_exclusion, role, user, datastore_latency. Look the body up first with describe_endpoint('<collection path>', 'POST'); most specs are polymorphic on type (see x-subtypes, e.g. VSphereBackupJobSpec/BackupJobSpec for job, WindowsLocalStorageSpec/LinuxHardenedStorageSpec/SmbStorageSpec for repository, ViHostSpec/CloudDirectorHostSpec for managed_server, StandardCredentialsSpec/LinuxCredentialsSpec for credentials). Additive, so no confirmation is needed by default; adding servers and repositories runs as a 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": {
      "kind": "<kind>",
      "spec": "<spec>"
    },
    "name": "create_object"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
specYes
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 readOnlyHint=false and destructiveHint=false; the description adds real value beyond them by noting the operation is additive (no confirmation by default) and that adding servers and repositories runs as a session, i.e. a long-running operation. It does not explain what happens on partial failure or what confirm_token does, which keeps it below a 5.

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-loads the action and the required lookup step, then packs the kind list and subtype examples densely. The subtype parenthetical is long but each example maps to a concrete kind, so it earns its space; the whole thing remains a single purposeful block.

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 polymorphic create tool with an output schema (so return values need no explanation), the definition covers the prerequisite discovery step, the polymorphic type field, the mutation semantics, and the long-running session cases. The only omission, confirm_token, is a minor schema-level detail rather than anything blocking correct invocation.

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 0%, so the description must carry parameter meaning. It fully documents `kind` (enumeration plus polymorphic subtype families) and explains that `spec` is an untyped POST body sourced from describe_endpoint, but `confirm_token` is never mentioned despite appearing in the schema — a meaningful gap given the description explicitly discusses confirmation behavior.

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 ('Create a VBR object from a full `spec`') and immediately defines what `spec` is (the POST body of its collection). The enumerated kinds list removes any ambiguity about what can be created and separates it cleanly from delete_object/update_object siblings.

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 an explicit prerequisite workflow: look the body up first with `describe_endpoint('<collection path>', 'POST')`, and warns that most specs are polymorphic on `type` with named subtypes per kind. It does not explicitly say when to prefer this over update_object for existing resources, but the create-vs-modify split is self-evident from the verb.

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