Skip to main content
Glama
mmpyro

vcluster-mcp

by mmpyro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

vcluster_list

List all virtual clusters in the current Kubernetes context. Optionally include creation timestamps or specify a kubeconfig path.

Instructions

List all vclusters in the current Kubernetes context.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fullNoAlso return the absolute Created timestamp, which AgeSeconds otherwise covers.
kubeconfig_pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.0.0
    • addedInput schema / properties / full
      Added value: +{
+  "default": false,
+  "description": "Also return the absolute Created timestamp, which AgeSeconds otherwise covers.",
+  "title": "Full",
+  "type": "boolean"
+}
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "anyOf": [
-        {
-          "additionalProperties": true,
-          "type": "object"
-        },
-        {
-          "items": {},
-          "type": "array"
-        },
-        {
-          "type": "string"
-        }
-      ],
-      "title": "Result"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "vcluster_listOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses the read-only nature implicitly ('List') and the scope ('current Kubernetes context'), but doesn't mention whether it requires a kubeconfig, what happens if no vclusters exist, or any side effects. For a list operation, the lack of explicit read-only confirmation and error behavior is a gap.

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?

One sentence, front-loaded with the action and resource. No wasted words. It earns its place by stating the scope ('current Kubernetes context').

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?

For a simple list tool with 2 optional parameters and no output schema, the description is mostly adequate. However, it doesn't explain the kubeconfig_path parameter's role or how the 'full' flag affects output beyond the schema's own description. The lack of annotations means the description should state that this is a read-only operation, which it only implies.

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 description coverage is 50%: the 'full' parameter is described in the schema, but 'kubeconfig_path' has no description. The tool description adds no parameter-level meaning beyond the schema. With 50% coverage, the description should compensate for the undocumented kubeconfig_path parameter, but it doesn't.

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 ('List') and resource ('vclusters') with a clear scope ('in the current Kubernetes context'). It distinguishes itself from siblings like vcluster_describe (which implies detail on one) and vcluster_create/delete (mutations), though it doesn't explicitly name an alternative.

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

Usage Guidelines3/5

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

The description implies usage: call it to list vclusters in the current context. It doesn't explicitly state when to use this vs vcluster_describe or when not to use it. The 'current Kubernetes context' phrase gives some context but no exclusions or alternatives.

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