Skip to main content
Glama

statefulset_get

Retrieve detailed information about a specific StatefulSet in Kubernetes, including its configuration and status, to monitor and manage stateful applications.

Instructions

Get details of a specific StatefulSet.

Args: context_name: The Kubernetes context name namespace: The Kubernetes namespace name: The StatefulSet name

Returns: Detailed information about the StatefulSet

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
context_nameYes
namespaceYes
nameYes

Implementation Reference

  • The statefulset_get tool implementation: decorated with @mcp.tool() for registration and executes the Kubernetes API call to retrieve StatefulSet details in the given namespace.
    @mcp.tool()
    @use_current_context
    def statefulset_get(context_name: str, namespace: str, name: str):
        """
        Get details of a specific StatefulSet.
    
        Args:
            context_name: The Kubernetes context name
            namespace: The Kubernetes namespace
            name: The StatefulSet name
    
        Returns:
            Detailed information about the StatefulSet
        """
        apps_v1: AppsV1Api = get_api_clients(context_name)["apps"]
        statefulset = apps_v1.read_namespaced_stateful_set(name=name, namespace=namespace)
        return {
            "name": statefulset.metadata.name,
            "replicas": statefulset.status.replicas,
            "labels": statefulset.metadata.labels,
            "containers": [c.image for c in statefulset.spec.template.spec.containers]
        }
  • Registers the statefulset_get function as an MCP tool.
    @mcp.tool()
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 states this is a read operation ('Get details'), which is clear, but doesn't disclose important behavioral traits: whether it requires specific permissions, what happens if the StatefulSet doesn't exist (error handling), rate limits, or what format the 'detailed information' returns. For a Kubernetes tool with zero annotation coverage, this is insufficient.

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?

Well-structured and appropriately sized. The first sentence clearly states the purpose, followed by organized sections for Args and Returns. Every sentence earns its place with no redundant information, making it easy to scan and understand.

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 complexity (Kubernetes StatefulSet operations), no annotations, no output schema, and 3 parameters with 0% schema coverage, the description is moderately complete. It covers the basic purpose and parameters but lacks behavioral context, error handling, and output details. For a read-only tool in this context, it's adequate but has clear gaps in guiding effective use.

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 0%, so the schema provides no parameter descriptions. The description adds basic semantics by explaining each parameter (context_name, namespace, name) in the Args section, which clarifies what each parameter represents. However, it doesn't provide format examples, constraints, or relationships between parameters. This partially compensates but doesn't fully address the coverage gap.

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 clearly states the tool's purpose as 'Get details of a specific StatefulSet' with a specific verb ('Get') and resource ('StatefulSet'). It distinguishes from siblings like statefulset_list (list vs get details) and statefulset_create/delete/update (mutations vs read). However, it doesn't explicitly mention how it differs from statefulset_list beyond 'details' vs 'list'.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. The description doesn't mention when to use statefulset_get versus statefulset_list (for listing multiple StatefulSets) or other get tools for different resources. It also doesn't specify prerequisites like cluster connectivity or authentication requirements.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bourbonkk/k8s-pilot'

If you have feedback or need assistance with the MCP directory API, please join our Discord server