Kubernetes Tools MCP Server

get_statefulset_summaries

Lists StatefulSet summaries for a given namespace or all namespaces, similar to kubectl get statefulsets. Provides replica counts, update strategy, and age.

Instructions

Retrieves a list of StatefulSetSummary objects for StatefulSets in a given namespace or all namespaces, similar to kubectl get statefulsets.

Parameters
----------
namespace : Optional[str], default=None
    The specific namespace to list StatefulSets from. If None, lists from all
    namespaces.

Returns
-------
list of StatefulSetSummary
    A list of StatefulSetSummary objects, each with the following fields:

    name : str
        Name of the StatefulSet.
    namespace : str
        Namespace in which the StatefulSet runs.
    total_replicas : int
        Desired number of replicas.
    ready_replicas : int
        Number of replicas currently ready.
    current_replicas : int
        Number of replicas created by the current revision.
    update_strategy : str
        Update strategy type (e.g. "RollingUpdate", "OnDelete").
    service_name : Optional[str]
        Name of the governing (headless) service.
    age : datetime.timedelta
        Age of the StatefulSet (current time minus creation timestamp).

Raises
------
K8sConfigError
    If unable to initialize the K8S API.
K8sApiError
    If the API call to list StatefulSets fails.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`namespace`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv2.1.0Oct 4, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and largely meets it: 'Retrieves' signals a read-only operation, and the Raises section names K8sConfigError and K8sApiError, telling the agent about init and API failure modes. It stops short of discussing pagination or large-cluster behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded and clear, but the description enumerates every field of StatefulSetSummary in a Returns block even though an output schema already exists, making it longer than necessary. The Raises block is useful; the field listing is largely redundant.

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

Completeness4/5

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

For a single-optional-parameter read tool, the description covers purpose, parameter semantics, and error modes adequately. Given that a return schema exists, the extra field enumeration is redundant rather than a completeness gap, so only minor context is missing.

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

Parameters4/5

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

Schema coverage is 0%, so the description must compensate, and it does: it explains that namespace is optional and that None means listing from all namespaces. That is exactly the semantic an agent needs, though it adds nothing about format or validation of the value.

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?

States a specific verb (Retrieves) and resource (StatefulSetSummary objects for StatefulSets), and scopes it to a namespace or all namespaces. The kubectl analogy and the resource-specific name distinguish it clearly from siblings like get_deployment_summaries and get_replicaset_summaries.

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?

Usage context is implied via 'in a given namespace or all namespaces' and the kubectl comparison, so an agent can infer this is a read/list operation. However, there is no explicit guidance on when to prefer this over sibling summary tools or any exclusions.

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