Skip to main content
Glama

list-resourcequotas

List Kubernetes resource quotas to monitor and manage namespace resource limits, ensuring cluster resource allocation compliance.

Instructions

List Kubernetes resource quotas in a namespace

Input Schema

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

Implementation Reference

  • The handler function for the 'list-resourcequotas' tool. It constructs and executes a 'kubectl get resourcequotas' command with an optional namespace flag, then returns the command output as text content.
    case "list-resourcequotas": {
      const { namespace } = args || {};
      const nsArg = namespace ? `-n ${namespace}` : "";
      const cmd = `kubectl get resourcequotas ${nsArg} -o wide`;
      const { stdout } = await execAsync(cmd);
      return {
        content: [{ type: "text", text: stdout || "No resource quotas found" }]
      };
    }
  • server.js:916-927 (registration)
    The tool registration entry in the tools array, including name, description, and input schema. This is returned by the ListTools handler.
      name: "list-resourcequotas",
      description: "List Kubernetes resource quotas in a namespace",
      inputSchema: {
        type: "object",
        properties: {
          namespace: { 
            type: "string",
            description: "The namespace to list resource quotas from (optional, defaults to current context namespace)"
          }
        }
      }
    },
  • The input schema definition for the 'list-resourcequotas' tool, specifying an optional 'namespace' parameter.
    inputSchema: {
      type: "object",
      properties: {
        namespace: { 
          type: "string",
          description: "The namespace to list resource quotas 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 full burden. While 'List' implies a read operation, it doesn't disclose important behavioral traits like whether authentication is required, if there are rate limits, what format the output takes, or if there are pagination considerations. The description is minimal and lacks operational context.

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 without any wasted words. It's appropriately sized for a simple listing tool and gets straight to the point.

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 simple listing tool with one optional parameter and no output schema, the description is minimally adequate. However, given the lack of annotations and the presence of many similar listing tools in the sibling set, more context about when to use this specific tool would improve completeness. The description meets basic requirements but doesn't excel.

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?

Schema description coverage is 100%, so the schema already fully documents the single optional parameter. The description doesn't add any parameter semantics beyond what's in the schema - it mentions 'in a namespace' which aligns with the parameter but provides no additional context about namespace selection or defaults.

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 resource quotas in a namespace'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'list-all' or 'list-namespaces', which could provide similar listing functionality for different 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. With many sibling listing tools (e.g., 'list-pods', 'list-configmaps', 'list-all'), there's no indication of when resource quotas specifically should be listed or what makes this tool the appropriate choice.

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