Skip to main content
Glama

list-serviceaccounts

Lists Kubernetes service accounts in a specified namespace to manage cluster access and permissions. Use this tool to view and audit service accounts for security and operational purposes.

Instructions

List Kubernetes service accounts in a namespace

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
namespaceNoThe namespace to list service accounts from (optional, defaults to current context namespace)

Implementation Reference

  • Handler for list-serviceaccounts tool: runs 'kubectl get serviceaccounts [namespace] -o wide' and returns the output.
    case "list-serviceaccounts": {
      const { namespace } = args || {};
      const nsArg = namespace ? `-n ${namespace}` : "";
      const cmd = `kubectl get serviceaccounts ${nsArg} -o wide`;
      const { stdout } = await execAsync(cmd);
      return {
        content: [{ type: "text", text: stdout || "No service accounts found" }]
      };
    }
  • Input schema definition for the list-serviceaccounts tool, accepting optional namespace.
      name: "list-serviceaccounts",
      description: "List Kubernetes service accounts in a namespace",
      inputSchema: {
        type: "object",
        properties: {
          namespace: { 
            type: "string",
            description: "The namespace to list service accounts from (optional, defaults to current context namespace)"
          }
        }
      }
    },
  • server.js:1392-1394 (registration)
    Registration of all tools list, including list-serviceaccounts, via the ListToolsRequestHandler.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools };
    });
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 the action ('List') but does not disclose behavioral traits like permissions needed, rate limits, pagination, output format, or error handling. This leaves significant gaps for a tool that interacts with Kubernetes resources.

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 is appropriately sized for a simple list tool, 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 no annotations and no output schema, the description is incomplete for a Kubernetes tool. It lacks details on behavior, output format, error cases, and how it differs from siblings, failing to provide sufficient context for safe and effective use by an AI agent.

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?

The input schema has 100% description coverage, with the parameter 'namespace' documented as optional and defaulting to the current context. The description does not add meaning beyond this, so it meets the baseline of 3 for high schema coverage without extra param details.

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 ('List') and resource ('Kubernetes service accounts in a namespace'), making the purpose specific and understandable. However, it does not explicitly differentiate from sibling tools like 'list-all' or 'list-pods', which would require a 5.

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-all' or other list-* tools. It lacks context about prerequisites, exclusions, or comparisons to siblings, offering minimal usage direction.

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/thekaranpargaie/kube-mcp'

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