Skip to main content
Glama

list-clusterrolebindings

Retrieve cluster role bindings in Kubernetes to manage access control and permissions across your cluster resources.

Instructions

List Kubernetes cluster role bindings

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler logic for the 'list-clusterrolebindings' tool. It runs the kubectl command to list clusterrolebindings with wide output and returns the result as text content.
    case "list-clusterrolebindings": {
      const cmd = `kubectl get clusterrolebindings -o wide`;
      const { stdout } = await execAsync(cmd);
      return {
        content: [{ type: "text", text: stdout || "No cluster role bindings found" }]
      };
    }
  • The tool definition including name, description, and empty input schema for 'list-clusterrolebindings'. This is used for registration and validation.
      name: "list-clusterrolebindings",
      description: "List Kubernetes cluster role bindings",
      inputSchema: {
        type: "object",
        properties: {}
      }
    },
  • server.js:1392-1394 (registration)
    Registers the list of all tools, including 'list-clusterrolebindings', for the ListToolsRequest.
    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. While 'List' implies a read-only operation, it doesn't specify output format, pagination behavior, permission requirements, or whether it shows all bindings or only those accessible to the current user. For a Kubernetes tool with zero annotation coverage, this leaves significant behavioral gaps.

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 states exactly what the tool does with zero wasted words. It's appropriately sized for a simple list operation and front-loads the essential information. Every word earns its place.

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 list tool with no output schema, the description is minimally complete - it tells you what resource you'll get. However, without annotations or output schema, it doesn't address important contextual aspects like permission requirements, output format, or how results are presented. The description meets basic requirements but leaves gaps an agent would need to discover through trial.

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 (schema coverage 100%), so no parameter documentation is needed. The description appropriately doesn't discuss parameters, focusing instead on the tool's purpose. With no parameters to document, this earns a high baseline score.

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 role bindings'), making the purpose immediately understandable. It distinguishes from siblings like 'list-rolebindings' (which are namespace-scoped) by specifying 'cluster' scope. However, it doesn't explicitly differentiate from 'list-all' which might include cluster role bindings among other resources.

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. It doesn't mention when you'd want cluster role bindings specifically versus regular role bindings, nor does it reference sibling tools like 'list-rolebindings' or 'list-all' as alternatives. The agent must infer usage context from the tool name alone.

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