Skip to main content
Glama
abhijeetka
by abhijeetka

get_namespaces

Retrieve all namespaces in a Kubernetes cluster to manage resources and organize workloads effectively.

Instructions

Get all namespaces in the cluster

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The tool handler function for 'get_namespaces'. It uses kubectl to fetch all namespaces in JSON format and returns the parsed JSON or an error dictionary.
    @mcp.tool()
    async def get_namespaces() -> dict:
        """Get all namespaces in the cluster"""
        try:
            cmd = ["kubectl", "get", "namespaces", "-o", "json"]
            result = subprocess.run(cmd, capture_output=True, text=True, check=True)
            return json.loads(result.stdout)
        except subprocess.CalledProcessError as e:
            return {"error": f"Failed to get namespaces: {str(e)}"}
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 states 'Get all namespaces' but doesn't clarify aspects like whether this requires specific permissions, how data is returned (e.g., pagination, format), or any rate limits. This leaves significant gaps for a tool in a Kubernetes context where such details are crucial.

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, efficient sentence with no wasted words, clearly front-loading the core action. It's appropriately sized for a simple tool with no parameters, making it highly concise and well-structured.

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 the complexity of Kubernetes tools and the lack of annotations and output schema, the description is insufficient. It doesn't explain return values, error handling, or behavioral traits like permissions or data format, leaving the agent with incomplete information for proper invocation.

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?

The input schema has 0 parameters with 100% coverage, meaning no parameters need documentation. The description doesn't add parameter details, which is acceptable here, but it could slightly enhance value by noting the lack of filters or options. Thus, it scores above baseline but not perfectly.

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 verb ('Get') and resource ('all namespaces in the cluster'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'list_contexts' or 'get_current_context', which might also retrieve cluster-related information, so it doesn't reach the highest score.

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?

The description provides no guidance on when to use this tool versus alternatives, such as 'list_contexts' or other 'get_' tools. It lacks context about prerequisites, exclusions, or specific scenarios where this tool is preferred, offering only a basic statement of function.

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/abhijeetka/mcp-k8s-server'

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