Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

List Replicas

list_replicas
Read-onlyIdempotent

List VM replicas or a replica's restore points, newest first, to select replicaPointIds for failover or failback. Read-only.

Instructions

List VM replicas, or - with replica_id - that replica's restore points (newest first), to pick the replicaPointIds for failover/failback. Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_replicas"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_pointsNo
replica_idNo
name_filterNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the closing 'Read-only.' largely restates structured data. The genuinely additive behavioral fact is the result ordering ('newest first'), which the schema does not convey; nothing is said about whether the replica list is paginated or whether `max_points` truncates results in a way that could hide restore points.

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, front-loaded with the primary operation and the conditional mode, with parameter names marked inline. Every clause carries information; no filler.

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?

There is no output schema, and the description compensates by stating what the restore-point listing contains and its ordering, plus the intended consumer of the IDs. It remains slightly incomplete about the replica-listing mode's contents and about how `max_points` constrains results, but for a 3-param read-only tool it is close to sufficient.

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 carries the full burden. It explains `replica_id` well by describing the mode switch to restore points, which is not derivable from the schema, but `max_points` and `name_filter` are never mentioned — notably, an agent is not told that `max_points` only matters in the restore-point mode, which could be misread as a limit on replicas.

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 (list VM replicas) and explicitly describes a second mode keyed on `replica_id` (that replica's restore points), with the ordering ('newest first') noted. An agent can distinguish this read/list tool from the mutation siblings failover_replicas/failback_replicas 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 concrete downstream purpose: gather `replicaPointIds` for failover/failback, and implicitly that this must be called before those operations. It does not address the nearest ambiguous alternative (rescan_replicas) or say when a rescan is needed first, so it stops short of full exclusion guidance.

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