Skip to main content
Glama
mmpyro

vcluster-mcp

by mmpyro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

vcluster_create

Create a virtual Kubernetes cluster in a host cluster without altering your active kube context.

Instructions

Create a vcluster. Never switches the caller's kube context.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
exposeNoCreate a load balancer service exposing the vcluster outside the host cluster.
valuesNoValues file paths; later files override earlier ones.
upgradeNo
namespaceNo
chart_nameNo
chart_repoNo
set_valuesNoInline helm values as dotted keys, e.g. {"sync.toHost.ingresses.enabled": "true"}.
chart_versionNo
kubeconfig_pathNo
create_namespaceNo
kube_config_context_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.0.0
    • addedInput schema / properties / expose / description
      Added value: +"Create a load balancer service exposing the vcluster outside the host cluster."
    • addedInput schema / properties / set_values / description
      Added value: +"Inline helm values as dotted keys, e.g. {\"sync.toHost.ingresses.enabled\": \"true\"}."
    • changedInput schema / properties / values / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / values / description
      Added value: +"Values file paths; later files override earlier ones."
    • changedOutput schema / (root)
      Previous value: -{
-  "$defs": {
-    "CommandResult": {
-      "properties": {
-        "exit_code": {
-          "title": "Exit Code",
-          "type": "integer"
-        },
-        "output": {
-          "title": "Output",
-          "type": "string"
-        }
-      },
-      "required": [
-        "exit_code",
-        "output"
-      ],
-      "title": "CommandResult",
-      "type": "object"
-    }
-  },
-  "properties": {
-    "result": {
-      "anyOf": [
-        {
-          "$ref": "#/$defs/CommandResult"
-        },
-        {
-          "additionalProperties": {
-            "type": "string"
-          },
-          "type": "object"
-        },
-        {
-          "type": "string"
-        }
-      ],
-      "title": "Result"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "vcluster_createOutput",
-  "type": "object"
-}New value: +null
  2. Changed9 schema fields changedv0.1.1
    • addedInput schema / properties / chart_name
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Chart Name"
+}
    • addedInput schema / properties / chart_repo
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Chart Repo"
+}
    • addedInput schema / properties / chart_version
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Chart Version"
+}
    • addedInput schema / properties / create_namespace
      Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Create Namespace"
+}
    • addedInput schema / properties / expose
      Added value: +{
+  "default": false,
+  "title": "Expose",
+  "type": "boolean"
+}
    • addedInput schema / properties / kube_config_context_name
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Kube Config Context Name"
+}
    • addedInput schema / properties / namespace
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Namespace"
+}
    • addedInput schema / properties / set_values
      Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Set Values"
+}
    • changedInput schema / properties / values / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
  3. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It does disclose a meaningful trait: 'Never switches the caller's kube context.' However, it doesn't mention other potential behaviors like permissions, side effects, or error conditions. This is a useful but partial disclosure, warranting a mid-range score.

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?

The description is extremely concise: two short sentences with no filler. It front-loads the primary action and includes a useful behavioral note. Every word earns its place, making it appropriately sized for the information it conveys.

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

Completeness1/5

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

For a tool with 12 parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain parameter semantics, expected side effects, prerequisites, or return behavior. The single behavioral note is insufficient for an agent to use this tool correctly without additional context.

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

Parameters1/5

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

Schema description coverage is only 25%, so the description should compensate by explaining parameters. The description does not mention any of the 12 parameters (name, expose, values, etc.). It adds zero meaning beyond what the schema already provides, and leaves the majority of parameters undefined.

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 clearly states the action: 'Create a vcluster.' This is a specific verb and resource, and it distinguishes from siblings like vcluster_list, vcluster_delete, etc. The additional note about not switching kube context adds clarity without ambiguity.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention context, prerequisites, or conditions favoring this over sibling tools. The verb 'create' implies usage, but there is no explicit or implied guidance beyond that.

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