k8scortex-mcp

list_vpas

List VerticalPodAutoscaler objects in a Kubernetes namespace to inspect their update mode and recommendation state.

Instructions

Lists VerticalPodAutoscaler objects in a namespace and their update mode/recommendation state.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "namespace": "<namespace>"
    },
    "name": "list_vpas"
  }
}

Input Schema

Name	Required	Description	Default
`cluster`	No	Target cluster name (default: 'default')
`namespace`	Yes	Namespace

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.2Jul 28, 2026

TDQS

A3.5/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states a read operation but does not clarify permissions, limits, error conditions, or whether it returns all VPAs. Minimal transparency beyond basic function.

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 a single sentence that conveys the essential purpose without any extraneous words. It is front-loaded and efficient.

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?

Given the lack of an output schema, the description partially compensates by mentioning 'update mode/recommendation state' but does not fully describe the output format or behavior (e.g., pagination, fields returned). Adequate but not complete.

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 coverage is 100%, so the schema already documents both parameters. The description adds no new semantic detail beyond what the schema provides, merely restating the namespace scope. Baseline 3 is appropriate.

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 specifies the action (Lists), resource (VerticalPodAutoscaler objects), scope (in a namespace), and additional detail (update mode/recommendation state). This distinguishes it from sibling tools like list_pods or get_vpa_recommendation.

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 the tool is used to list VPAs in a namespace but provides no explicit guidance on when to use it versus alternatives, no filtering criteria, and no exclusions. It is adequate but lacks proactive direction.

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

Deploy Server