Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Discover Cloud Director Vcenters

discover_cloud_director_vcenters
Read-onlyIdempotent

Lists vCenter Servers attached to a VMware Cloud Director server to verify them before adding the Cloud Director host. Read-only discovery for integration planning.

Instructions

List the vCenter Servers attached to a VMware Cloud Director server, before adding it (CloudDirectorHostDiscoverySpec: see describe_model). Read-only.

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": {
      "spec": "<spec>"
    },
    "name": "discover_cloud_director_vcenters"
  }
}

Input Schema

NameRequiredDescriptionDefault
specYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so "Read-only" at the end of the description is pure repetition. The genuinely additive piece is the pointer to `CloudDirectorHostDiscoverySpec` and describe_model, which tells the agent the opaque spec object has a documented shape elsewhere. Nothing is said about whether this queries the live VCD endpoint or what happens on an unreachable server.

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?

One compact sentence with the action and scope front-loaded, followed by a short parenthetical pointer. The trailing "Read-only" is the only piece that fails to earn its place since annotations already cover it.

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?

No output schema exists, yet the description says nothing about the return shape (e.g. a list of vCenter names/endpoints, or how an empty result is represented). The opaque required parameter is at least routed to describe_model. Adequate to invoke, but thin for a discovery tool whose whole output is the value.

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 coverage is 0% and the single parameter is a free-form nested object with additionalProperties, so the schema gives an agent essentially nothing. The description partially compensates by naming the expected model type and directing the caller to describe_model, but it does not describe any field of the spec.

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 and resource: listing the vCenter Servers attached to a VMware Cloud Director server. That is concrete enough to distinguish it from siblings like api_read or manage_discovered_computers, though it never names an alternative discovery tool explicitly.

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?

"before adding it" gives a clear use context: pre-flight discovery ahead of registration. There are no explicit exclusions or named alternatives, which is what separates a 4 from a 5.

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