Skip to main content
Glama
vmware-skills

vmware-vks

by vmware-skills
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

create_namespace

Preview and create vSphere Namespaces on a Supervisor Cluster, showing 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesNamespace name (lowercase, no spaces).
targetNovCenter in config.yaml; omit for the default.
confirmNoFalse (default) returns the blast radius and changes nothing. True applies it.
dry_runNoDeprecated alias for confirm; removed in the next minor release. dry_run=False acts, dry_run=True previews.
cpu_limitNoMHz. Omit for no limit.
cluster_idYesSupervisor MoRef (from check_vks_compatibility).
descriptionNoFree-text label. Omit for none.
storage_policyYesPolicy ID (from list_supervisor_storage_policies).
memory_limit_mibNoMiB. Omit for no limit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.11.0
    • 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"
  2. Changed9 schema fields changedv1.8.14
    • 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."
  3. Addedv1.8.9
  4. Removedv1.8.8
  5. Addedv1.5.26
  6. Removedv1.5.23
  7. First observedv1.3.2

TDQS

A4.9/5.0
Behavior5/5

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

The description goes far beyond the annotations by explaining the preview-only default, the exact return shape for confirm=True, refusal conditions, and the required confirmation workflow. This is especially valuable because the annotations only indicate readOnly=false and idempotent=false; the description reveals the nuanced two-phase behavior.

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?

Every sentence earns its place. The description is front-loaded with the core purpose, then efficiently covers preview behavior, user decision, refusal conditions, and follow-up verification. It is detailed but not bloated, and the structure guides the agent through the correct call sequence.

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?

For a 9-parameter creation tool with no output schema, the description is remarkably complete. It explains the preview return, the confirmed return, failure modes, and post-creation verification. It also refers agents to the right sibling tools for name conflicts and verification, leaving no critical ambiguity for correct invocation.

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 already 100%, but the description adds meaningful parameter-level context by explaining what confirm actually controls, what blast_radius contains, and why the agent should not set confirm=True unilaterally. It doesn't repeat every parameter, but it clarifies the most behaviorally important one beyond the schema.

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?

The description opens with a specific verb and resource: 'Create a vSphere Namespace on a Supervisor Cluster.' It clearly distinguishes this creation tool from sibling operations like update_namespace, delete_namespace, and get_namespace, and the [WRITE] tag reinforces that this is a mutating operation.

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?

The description provides explicit usage rules: without confirm=True it only previews, the user must see the preview before confirming, and the agent must not set confirm=True on its own. It also names alternatives directly: use update_namespace when the name is taken, and verify with get_namespace afterwards.

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

Deploy Server

Other Tools