Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Set Agent Backup Attachment

set_agent_backup_attachment
Destructive

Attaches existing backups to a managed agent computer or detaches them, useful after reinstalling the agent or restoring its backup associations.

Instructions

Attach existing backups to a managed agent computer (e.g. after reinstalling it), or detach them.

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": {
      "discovered_entity_id": "<discovered_entity_id>",
      "backup_ids": "<backup_ids>",
      "attach": "<attach>"
    },
    "name": "set_agent_backup_attachment"
  }
}

Input Schema

NameRequiredDescriptionDefault
attachYes
backup_idsYes
confirm_tokenNo
discovered_entity_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, and the word "detach" is consistent with that. The description adds the reinstall context for the attach case, but it does not address the confirm_token parameter, which is significant for a destructive, non-idempotent operation, nor does it say whether attachment changes existing backup state or whether detaching preserves data.

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?

A single tight sentence with the core action front-loaded and the example scenario trailing it. Nothing is wasted, though the space saved is space that parameter and safety detail could have used.

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

Completeness2/5

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

This is a destructive, non-idempotent mutation with four undocumented parameters and only a one-line description. The output schema means return values need not be described, but the confirmation-token requirement and the effect of detaching on retained backups are gaps an agent needs filled before calling it.

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% across four parameters, so the description must carry the burden and largely does not. "Attach ... or detach them" loosely maps to the boolean attach flag and hints that backup_ids is a collection, but discovered_entity_id and especially confirm_token (default null) are never explained.

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?

The description states a specific verb pair (attach/detach) and a specific resource (existing backups to a managed agent computer), which matches the tool name and lets an agent distinguish this from backup-moving or backup-deleting siblings. It stops short of naming any sibling to contrast with, so 4 rather than 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?

The parenthetical "e.g. after reinstalling it" gives one concrete triggering scenario, which is useful implied guidance. There is no statement of when NOT to use it, no mention of prerequisites or required permissions, and no pointer to an alternative for related operations (copy/move/delete backup).

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