Skip to main content
Glama

list-gke-clusters

Retrieve all Google Kubernetes Engine clusters in your current GCP project to manage containerized applications and resources.

Instructions

List all GKE clusters in the current project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
locationNoLocation (region or zone) to list clusters from (defaults to all locations)

Implementation Reference

  • index.ts:171-184 (registration)
    Tool registration in the listTools response, including name, description, and input schema.
    {
      name: "list-gke-clusters",
      description: "List all GKE clusters in the current project",
      inputSchema: {
        type: "object",
        properties: {
          location: {
            type: "string",
            description: "Location (region or zone) to list clusters from (defaults to all locations)",
          }
        },
        required: [],
      },
    },
  • Zod schema for validating input arguments of the list-gke-clusters tool.
    const ListGKEClustersSchema = z.object({
      location: z.string().optional(),
    });
  • Executes the list-gke-clusters tool: validates input, lists clusters using ClusterManagerClient.listClusters, formats output as JSON with cluster details.
    } else if (name === "list-gke-clusters") {
      const { location } = ListGKEClustersSchema.parse(args);
      
      if (!selectedProject) {
        return createTextResponse("No project selected. Please select a project first.");
      }
    
      try {
        const containerClient = new ClusterManagerClient();
        const parent = location 
          ? `projects/${selectedProject}/locations/${location}`
          : `projects/${selectedProject}/locations/-`;
        
        const [clusters] = await containerClient.listClusters({ parent });
        
        return createTextResponse(JSON.stringify({
          clusters: clusters.clusters?.map((cluster: any) => ({
            name: cluster.name || null,
            location: cluster.location || null,
            status: cluster.status || null,
            nodeCount: cluster.currentNodeCount || null,
            k8sVersion: cluster.currentMasterVersion || null
          })) || []
        }, null, 2));
      } catch (error: any) {
        console.error('Error listing GKE clusters:', error);
        return createTextResponse(`Error listing GKE clusters: ${error.message}`);
      }
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 it's a list operation, implying read-only behavior, but doesn't cover aspects like permissions required, rate limits, pagination, or what 'current project' means in context. This leaves significant gaps for an agent to understand how to use it effectively.

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, direct sentence that efficiently conveys the core action and resource without any fluff or redundancy. It's front-loaded with the key information, making it easy for an agent to parse quickly.

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, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose but lacks details on behavior, usage context, or output format, which could hinder an agent's ability to use it correctly in more complex scenarios.

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 'location' parameter clearly documented in the schema. The description doesn't add any parameter-specific details beyond implying a scope ('in the current project'), which aligns with the schema's default behavior. This meets the baseline for high schema coverage.

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 all') and resource ('GKE clusters in the current project'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'list-projects' or 'list-sql-instances' beyond specifying the resource type, which keeps it from a perfect 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 whether it's for inventory checks, monitoring, or setup purposes. It also doesn't mention prerequisites like needing a selected project or compare it to siblings like 'list-projects' for broader context.

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/RadiumGu/gcp-ops-mcp'

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