Skip to main content
Glama
mmpyro

vcluster-mcp

by mmpyro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

vcluster_call

Execute shell commands inside a vcluster through vcluster connect, enabling direct inspection and management of virtual cluster resources.

Instructions

Run a command inside a vcluster via vcluster connect.

Output is capped; prefer narrow queries over -o yaml across all namespaces.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
commandYesCommand to run inside the vcluster, standard shell quoting, e.g. "kubectl get pods -n default".
namespaceNo
kubeconfig_pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.0.0
    • addedInput schema / properties / command / description
      Added value: +"Command to run inside the vcluster, standard shell quoting, e.g. \"kubectl get pods -n default\"."
    • 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_callOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions that output is capped, which is useful, but does not disclose side effects, authentication/connection requirements, failure behavior, or the fact that arbitrary commands may have cluster-wide impact.

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?

The description is compact and front-loaded with the primary action, and the additional output-cap warning earns its place. It is lean, though slightly under-specified for the number of parameters involved.

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

Completeness2/5

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

Given no output schema, no annotations, and sparse parameter documentation, the description leaves important context missing: what the command result looks like, how optional parameters behave, and whether any preconditions exist before invoking the vcluster. The output cap notice is the only contextual detail provided.

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

Parameters2/5

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

Schema description coverage is only 25%, with just the command parameter described. The description provides general advice about narrow queries but does not explain the semantics of name, namespace, or kubeconfig_path, leaving the agent to infer them from names alone.

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 states a specific verb and resource: 'Run a command inside a vcluster via vcluster connect.' This clearly distinguishes it from the sibling tools like vcluster_kubeconfig, vcluster_pause, and vcluster_describe.

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 gives operational guidance ('prefer narrow queries over -o yaml across all namespaces') and warns about output capping, which implies this tool is for targeted queries. However, it does not explicitly state when to use this tool versus alternatives or when not to use it.

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