Get status, resources, and configuration for a specific virtual cluster. Specify the cluster name to view its details.
Status, resources and configuration of one vcluster. Namespace defaults to vcluster-.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | ||
| namespace | No | ||
| kubeconfig_path | No |
Changes observed during successful MCP inspections.
v2.0.0Output schema / (root)Previous value: -{
- "properties": {
- "result": {
- "anyOf": [
- {
- "additionalProperties": true,
- "type": "object"
- },
- {
- "type": "string"
- }
- ],
- "title": "Result"
- }
- },
- "required": [
- "result"
- ],
- "title": "vcluster_describeOutput",
- "type": "object"
-}New value: +nullv0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the disclosure burden. It reveals the namespace default behavior and that the tool surfaces status/resources/configuration, but it does not state whether the operation is read-only, what output format is returned, or whether a kubeconfig is required.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences with no filler; the core purpose is front-loaded and the namespace default follows as a useful clarification.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with no annotations and no output schema, the description should cover return format, parameter meaning, and behavior. It covers purpose and namespace default but omits kubeconfig_path semantics and any output/error behavior, leaving an agent to guess.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must explain parameters. It only adds meaning for namespace by giving the vcluster-<name> default; name is left implicit and kubeconfig_path is completely unexplained.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states the tool returns status, resources, and configuration for a single vcluster, which is a clear scope and distinguishes it from vcluster_list. It lacks an explicit verb, relying on the tool name 'describe', and does not specify what 'resources' or 'configuration' include.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The 'one vcluster' wording implies this is for inspecting a single vcluster rather than listing all clusters, but no alternatives or exclusions are named. The namespace default is helpful execution context, not tool-selection guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.