Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Update Object

update_object
Destructive

Edit existing VBR objects by passing only changed fields; deep-merges changes and shows a field-level diff before applying. Use replace=True to send a full replacement body.

Instructions

Edit an existing VBR object: pass only the fields to change in changes; the tool reads the object, deep-merges changes into it and sends the complete model (VBR PUT replaces the whole object). Nested objects merge field by field; lists are replaced as a whole, so send the full new list. replace=True sends changes as the complete body instead.

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 (not ad_domain). user edits the role list, global_vm_exclusion the note, encryption_password the hint. The confirmation plan shows a field-level diff. Example: disable job encryption -> kind='job', changes={'storage': {'advancedSettings': {'storageData': {'encryption': {'isEnabled': false}}}}}. Edits can change what is protected and how: 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>",
      "id": "<id>",
      "changes": "<changes>"
    },
    "name": "update_object"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
kindYes
changesYes
replaceNo
confirm_tokenNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already flag destructive/not-idempotent, and the description adds real substance: the tool reads the object, deep-merges, then PUTs the complete model, nested objects merge per field while lists are replaced, and a confirmation plan shows a field-level diff. It stops short of explaining how `confirm_token` is obtained or that the edit is unconfirmed until the token is supplied.

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 the merge contract, then kinds, then a worked example — every block earns its place. Dense but well organized; the parenthetical '(not `ad_domain`)' adds noise rather than clarity.

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?

For a destructive, five-parameter, nested-object mutation with an output schema, the description covers the semantics that matter most (partial update, merge, list replacement). The remaining gap is the confirm/apply lifecycle around `confirm_token`, which the phrase 'confirmed by the server' only gestures at.

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 load, and it does for `changes` (merge semantics, list replacement), `replace`, and `kind` with a full enumeration that also matches the schema. `id` and `confirm_token` remain unexplained, and the '(not `ad_domain`)' note is unclear since `ad_domain` is a valid enum value.

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 ('Edit an existing VBR object') and immediately scopes it with the supported object kinds, so an agent can tell it apart from create_object and delete_object 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 explicit mechanics for when to use partial `changes` versus `replace=True`, and notes lists must be sent whole. What's missing is a pointer to alternatives such as api_write or update_settings when the change isn't a supported object edit.

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