Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Rescan Inventory

rescan_inventory

Refresh the cached virtualization inventory for one managed server when newly created VMs or vApps do not appear in browse_inventory.

Instructions

Refresh the cached virtualization inventory (VMs, vApps, datastores, networks) of one managed server, e.g. after a VM or vApp was created and does not show up in browse_inventory yet.

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": {
      "hostname": "<hostname>"
    },
    "name": "rescan_inventory"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostnameYesManaged server name as VBR shows it, e.g. 'vcenter01.corp.local'.
confirm_tokenNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the description only needs to add context; it does clarify that the operation is a cache refresh (bounded, non-destructive), which is useful. However, it says nothing about how long a rescan takes or whether it is synchronous, nor anything about the confirm_token, which is the most behaviorally significant unknown for this tool.

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 compact sentences, front-loaded with the resource and scope, followed by the usage trigger. No redundant restatement of the title or schema fields.

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 explained, and the hostname parameter is covered by the schema. The definition is still incomplete for a non-read-only refresh operation: confirm_token semantics and expected duration/completion behavior are left for the agent to guess.

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?

hostname is fully documented in the schema itself, so the description adds nothing there beyond the 'one managed server' framing. The confirm_token parameter has no description in either the schema or the prose, and the description does not explain when or why a token is required for this rescan.

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 ('Refresh') plus the exact resource ('cached virtualization inventory') and enumerates its contents (VMs, vApps, datastores, networks) with the scope 'one managed server'. It also names the sibling it complements (browse_inventory), so an agent can distinguish it from browse_inventory and from the other rescan_* tools without opening a 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 a concrete trigger condition: when a VM or vApp was created but does not yet appear in browse_inventory. That implies the read-only alternative (browse first, rescan only if stale), but no explicit when-not-to-use or cost/latency caveat (e.g. avoid rescans on a schedule) is stated.

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