Skip to main content
Glama

argocd-list-apps

List ArgoCD applications to monitor deployments and manage Kubernetes resources through the Kubernetes MCP Server.

Instructions

List ArgoCD applications

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
namespaceNoThe namespace to list apps from (optional, defaults to argocd namespace)

Implementation Reference

  • Handler implementation for the 'argocd-list-apps' tool. Executes 'kubectl get applications' in the specified namespace (default: argocd) to list ArgoCD applications.
    case "argocd-list-apps": {
      const { namespace = "argocd" } = args || {};
      const cmd = `kubectl get applications -n ${namespace} -o wide`;
      const { stdout } = await execAsync(cmd);
      return {
        content: [{ type: "text", text: stdout || "No ArgoCD applications found" }]
      };
    }
  • server.js:1255-1267 (registration)
    Tool registration definition for 'argocd-list-apps', including name, description, and input schema. This object is part of the 'tools' array returned by ListToolsRequestHandler.
      name: "argocd-list-apps",
      description: "List ArgoCD applications",
      inputSchema: {
        type: "object",
        properties: {
          namespace: { 
            type: "string",
            description: "The namespace to list apps from (optional, defaults to argocd namespace)"
          }
        }
      }
    },
    {
  • Input schema definition for the 'argocd-list-apps' tool, defining optional 'namespace' parameter.
      name: "argocd-list-apps",
      description: "List ArgoCD applications",
      inputSchema: {
        type: "object",
        properties: {
          namespace: { 
            type: "string",
            description: "The namespace to list apps from (optional, defaults to argocd 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. 'List ArgoCD applications' implies a read-only operation but doesn't specify authentication requirements, rate limits, pagination behavior, or what happens when namespace isn't provided. For a tool with zero annotation coverage, this is insufficient behavioral disclosure.

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 phrase that communicates the core purpose 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 100% schema coverage, the description is minimally adequate. However, without annotations or output schema, the agent lacks information about authentication requirements, response format, and how this differs from other listing tools. The description meets basic requirements but could provide more context.

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%, with the single parameter 'namespace' well-documented in the schema. The description adds no additional parameter information beyond what's already in the structured schema. With high schema coverage, the baseline score of 3 is appropriate.

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 'List ArgoCD applications' clearly states the verb ('List') and resource ('ArgoCD applications'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'list-all' or 'list-pods' - the agent must infer that this specifically lists ArgoCD applications rather than general Kubernetes 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 available (list-all, list-pods, list-deployments, etc.), the agent must deduce from the name 'argocd-list-apps' that this is for ArgoCD-specific applications rather than general Kubernetes resources.

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