Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

High Availability Cluster

high_availability_cluster
Destructive

Perform planned switchover to the secondary node or failover when the primary node is lost, optionally skipping replication lag checks, then reconnect to the new primary.

Instructions

Backup server High Availability cluster: planned switchover to the secondary node (ignore_lag skips the database replication lag check), or failover when the primary node is lost. The REST API and this MCP server reconnect to the new primary only if VBR_BASE_URL points at the cluster's shared name.

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": {
      "action": "<action>"
    },
    "name": "high_availability_cluster"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
ignore_lagNo
confirm_tokenNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already flag destructive=true and non-idempotent, and the description adds genuinely non-obvious behavior: ignore_lag suppresses the replication-lag gate, and the API/MCP server only reconnects to the new primary if VBR_BASE_URL uses the cluster shared name. That last caveat is critical operational context an agent would otherwise miss. It does not explain how confirmation is obtained or what happens to the demoted/lost node, and confirm_token is never mentioned.

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?

Two sentences, densely packed with distinct information, front-loaded with the resource. Every clause (lag check, reconnection precondition) earns its place; no filler.

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?

An output schema exists so return values need not be described, and the cluster/reconnection model is covered. However, for a destructive, non-idempotent cluster operation the definition omits the confirm_token mechanism, expected post-operation state, and any partial-failure behavior — enough gaps that an agent could invoke it incorrectly.

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 description coverage is 0%, so the description must carry parameter meaning. It explains action's two values well and explains what ignore_lag actually skips, but confirm_token — plausibly the safety gate on a destructive operation — is completely undefined (source, format, whether it is required).

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?

Names a concrete resource (backup server High Availability cluster) and two distinct operations (planned switchover, failover on primary loss), which is far more specific than the bare title. It does not explicitly separate itself from the similarly named failover_replicas/failback_replicas siblings, so an agent must still infer that this concerns the HA cluster rather than replicas.

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?

Explicitly states the selection condition for each action: switchover for planned moves, failover only when the primary node is lost. No when-not-to-use guidance or prerequisite checks (e.g., node health preconditions) are given, but the core routing decision is clear.

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