Skip to main content
Glama

list-clusterroles

Retrieve and display all Kubernetes cluster roles to manage access control and permissions across your cluster.

Instructions

List Kubernetes cluster roles

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'list-clusterroles' tool. It executes the kubectl command 'kubectl get clusterroles -o wide' and returns the output as text content or a fallback message if no output.
    case "list-clusterroles": {
      const cmd = `kubectl get clusterroles -o wide`;
      const { stdout } = await execAsync(cmd);
      return {
        content: [{ type: "text", text: stdout || "No cluster roles found" }]
      };
    }
  • The tool definition including name, description, and empty input schema (no parameters required) used for tool listing and validation.
    {
      name: "list-clusterroles",
      description: "List Kubernetes cluster roles",
      inputSchema: {
        type: "object",
        properties: {}
      }
  • server.js:1392-1394 (registration)
    Registration of the tool list handler, which returns the full tools array containing 'list-clusterroles' for tool discovery.
    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 full burden for behavioral disclosure. 'List' implies a read operation, but the description doesn't specify whether this returns all cluster roles, if there's pagination, what format the output takes, or any authentication requirements. For a tool with zero annotation coverage, this leaves significant behavioral questions unanswered.

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 that communicates the essential purpose without any wasted words. It's appropriately sized for a simple listing operation and gets straight to the point with no 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?

For a zero-parameter listing tool, the description covers the basic purpose adequately. However, without annotations or an output schema, it doesn't address important behavioral aspects like output format, pagination, or error conditions. The description is minimally viable but leaves gaps that would help an agent use the tool effectively.

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 tool has zero parameters with 100% schema description coverage, so the schema already fully documents the parameter situation. The description appropriately doesn't discuss parameters since none exist, maintaining focus on the tool's purpose rather than attempting to document non-existent inputs.

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 cluster roles'), making the purpose immediately understandable. It distinguishes from other list tools by specifying the exact resource type, though it doesn't explicitly differentiate from similar tools like list-roles or list-clusterrolebindings beyond the resource name.

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. With sibling tools like list-roles, list-clusterrolebindings, and list-all available, there's no indication of when this specific listing operation is preferred or what distinguishes it from other listing mechanisms.

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