vmware-vks

create_namespace

Creates a vSphere Namespace on a Supervisor Cluster, with a preview mode that shows the blast radius before applying changes.

Instructions

[WRITE] Create a vSphere Namespace on a Supervisor Cluster.

Without confirm=True this only previews: it returns blast_radius (the spec that would be applied, and whether the name is already taken) and creates nothing. Show it to the user and get their decision. Do not set confirm=True on your own because the user asked earlier — they have not seen the preview yet. confirm=True returns {action: "created", namespace, status, cluster, blast_radius}; it is refused when the name is taken (use update_namespace) or the existing names could not be read. Confirm with get_namespace afterwards.

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": {
      "name": "<name>",
      "cluster_id": "<cluster_id>",
      "storage_policy": "<storage_policy>"
    },
    "name": "create_namespace"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Namespace name (lowercase, no spaces).
`target`	No	vCenter in config.yaml; omit for the default.
`confirm`	No	False (default) returns the blast radius and changes nothing. True applies it.
`cpu_limit`	No	MHz. Omit for no limit.
`cluster_id`	Yes	Supervisor MoRef (from check_vks_compatibility).
`description`	No	Free-text label. Omit for none.
`storage_policy`	Yes	Policy ID (from list_supervisor_storage_policies).
`memory_limit_mib`	No	MiB. Omit for no limit.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv3.4.2Oct 31, 2026

removedInput schema / properties / dry_run

Removed value: -{
-  "anyOf": [
-    {
-      "type": "boolean"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Deprecated alias for confirm; removed in the next minor release. dry_run=False acts, dry_run=True previews.",
-  "title": "Dry Run"
-}

Changed5 schema fields changedv1.11.0Sep 20, 2026

addedInput schema / properties / confirm

Added value: +{
+  "default": false,
+  "description": "False (default) returns the blast radius and changes nothing. True applies it.",
+  "title": "Confirm",
+  "type": "boolean"
+}

addedInput schema / properties / dry_run / anyOf

Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / dry_run / default
```
Previous value: -trueNew value: +null
```

changedInput schema / properties / dry_run / description

Previous value: -"Preview only (default: True)."New value: +"Deprecated alias for confirm; removed in the next minor release. dry_run=False acts, dry_run=True previews."

removedInput schema / properties / dry_run / type
```
Removed value: -"boolean"
```

Changed9 schema fields changedv1.8.14Aug 30, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / cluster_id / description
```
Added value: +"Supervisor MoRef (from check_vks_compatibility)."
```
- addedInput schema / properties / cpu_limit / description
```
Added value: +"MHz. Omit for no limit."
```
- addedInput schema / properties / description / description
```
Added value: +"Free-text label. Omit for none."
```
- addedInput schema / properties / dry_run / description
```
Added value: +"Preview only (default: True)."
```
- addedInput schema / properties / memory_limit_mib / description
```
Added value: +"MiB. Omit for no limit."
```
- addedInput schema / properties / name / description
```
Added value: +"Namespace name (lowercase, no spaces)."
```
- addedInput schema / properties / storage_policy / description
```
Added value: +"Policy ID (from list_supervisor_storage_policies)."
```
- addedInput schema / properties / target / description
```
Added value: +"vCenter in config.yaml; omit for the default."
```
Addedv1.8.9Aug 1, 2026
Removedv1.8.8Jul 22, 2026
Addedv1.5.26May 20, 2026
Removedv1.5.23May 20, 2026
First observedv1.3.2Mar 27, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only say readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true; the description adds the substance: no side effects without confirm, the exact preview payload (blast_radius plus name-availability check), the exact success payload {action, namespace, status, cluster, blast_radius}, and two distinct refusal conditions. This is well beyond what the annotations convey.

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?

Front-loaded with the [WRITE] marker and the one-line purpose, then the safety-critical preview rule before the mechanics. Dense but nearly every clause carries operational meaning; the explicit anti-footgun sentence about prior user requests is slightly verbose but justified by the risk profile.

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

Completeness5/5

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

With 8 parameters, no output schema, and a destructive-adjacent write operation, the description supplies the missing return shapes, the refusal conditions, and the follow-up verification call. Nothing an agent needs to invoke this safely and correctly is absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so cluster_id, storage_policy, name, and the limit fields are already documented (including their sibling-tool provenance), which sets a baseline of 3. The description earns above baseline by elaborating the confirm parameter's two modes, its return payload, and the conditions under which it is refused.

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?

Specific verb + resource ("Create a vSphere Namespace on a Supervisor Cluster") plus a [WRITE] tag that immediately classifies the operation. Sibling tools include update_namespace and delete_namespace, and the description makes the create-vs-update boundary explicit by naming update_namespace for the name-taken case.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when/when-not: default (confirm=false) is a preview to be shown to the user, and confirm=True must not be set on the agent's own initiative. It also routes to the correct alternative ("refused when the name is taken (use update_namespace)") and names a verification step (get_namespace).

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