Skip to main content
Glama

list-roles

List Kubernetes roles in a specified namespace to manage access permissions and security policies within your cluster.

Instructions

List Kubernetes roles in a namespace

Input Schema

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

Implementation Reference

  • The execution handler for the 'list-roles' tool. It extracts the optional namespace from arguments, constructs a kubectl command to list roles with wide output, executes it using execAsync, and returns the stdout as text content or 'No roles found' if empty.
    case "list-roles": {
      const { namespace } = args || {};
      const nsArg = namespace ? `-n ${namespace}` : "";
      const cmd = `kubectl get roles ${nsArg} -o wide`;
      const { stdout } = await execAsync(cmd);
      return {
        content: [{ type: "text", text: stdout || "No roles found" }]
      };
    }
  • server.js:822-833 (registration)
    The tool registration object for 'list-roles', included in the tools array returned by ListToolsRequestSchema handler. Defines the tool name, description, and input schema with optional namespace parameter.
      name: "list-roles",
      description: "List Kubernetes roles in a namespace",
      inputSchema: {
        type: "object",
        properties: {
          namespace: { 
            type: "string",
            description: "The namespace to list roles from (optional, defaults to current context namespace)"
          }
        }
      }
    },
  • The input schema for the 'list-roles' tool, defining an optional 'namespace' string parameter.
    inputSchema: {
      type: "object",
      properties: {
        namespace: { 
          type: "string",
          description: "The namespace to list roles from (optional, defaults to current context namespace)"
        }
      }
    }
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 of behavioral disclosure. It states it's a list operation, implying read-only behavior, but doesn't mention output format, pagination, error conditions, or authentication requirements. For a tool with zero annotation coverage, this leaves significant gaps in understanding how it behaves.

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, clear sentence with no wasted words. It's front-loaded with the core purpose and efficiently communicates the essential information without unnecessary elaboration.

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 tool's low complexity (one optional parameter) and high schema coverage, the description is minimally adequate. However, with no annotations and no output schema, it should ideally provide more context about the return format or typical usage scenarios to help an agent understand what to expect from this operation.

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 schema description coverage is 100%, with the single parameter 'namespace' fully documented in the schema. The description doesn't add any additional meaning beyond what's in the schema (e.g., it doesn't clarify default behavior or namespace constraints), so it meets the baseline score when schema coverage is high.

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 action ('List') and resource ('Kubernetes roles in a namespace'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'list-clusterroles' or 'list-rolebindings', which would require mentioning it's specifically for namespace-scoped roles rather than cluster-wide roles.

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 is provided on when to use this tool versus alternatives. The description doesn't mention sibling tools like 'list-clusterroles' for cluster-scoped roles or 'list-rolebindings' for related resources, nor does it specify prerequisites or typical use cases for listing roles.

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