Skip to main content
Glama
argoproj-labs

argocd-mcp

Official

get_application

Retrieve ArgoCD application details by name and optional namespace to monitor deployment status and configurations.

Instructions

get_application returns application by application name. Optionally specify the application namespace to get applications from non-default namespaces.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
applicationNameYes
applicationNamespaceNoThe namespace where the ArgoCD application resource will be created. This is the namespace of the Application resource itself, not the destination namespace for the application's resources. You can specify any valid Kubernetes namespace (e.g., 'argocd', 'argocd-apps', 'my-namespace', etc.). The default ArgoCD namespace is typically 'argocd', but you can use any namespace you prefer.

Implementation Reference

  • Registration of the 'get_application' tool, including input schema and thin handler that delegates to ArgoCD client
    this.addJsonOutputTool(
      'get_application',
      'get_application returns application by application name. Optionally specify the application namespace to get applications from non-default namespaces.',
      {
        applicationName: z.string(),
        applicationNamespace: ApplicationNamespaceSchema.optional()
      },
      async ({ applicationName, applicationNamespace }) =>
        await this.argocdClient.getApplication(applicationName, applicationNamespace)
    );
  • Core handler function in ArgoCD client that performs the HTTP GET request to retrieve the application details from the ArgoCD API
    public async getApplication(applicationName: string, appNamespace?: string) {
      const queryParams = appNamespace ? { appNamespace } : undefined;
      const { body } = await this.client.get<V1alpha1Application>(
        `/api/v1/applications/${applicationName}`,
        queryParams
      );
      return body;
    }
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 this is a read operation ('returns'), which is helpful, but doesn't describe what happens if the application doesn't exist (e.g., error behavior), whether authentication is required, rate limits, or the format/structure of the returned application data. For a read 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 efficiently structured in two clear sentences: the first states the core purpose, and the second explains the optional parameter. There's no wasted language, and the information is front-loaded with the main function followed by the qualification. Every sentence earns its place by adding distinct value.

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 moderate complexity (2 parameters, no output schema, no annotations), the description is adequate but incomplete. It covers the basic purpose and parameter usage but lacks details about error conditions, return format, authentication requirements, or how it differs from sibling tools. Without annotations or output schema, the description should do more to compensate, particularly for behavioral aspects.

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 description adds meaningful context about the optional namespace parameter, explaining it's for 'non-default namespaces' which clarifies its purpose beyond what the schema provides. With 50% schema description coverage (only applicationNamespace has a description), the description compensates by providing additional semantic information about when to use the namespace parameter, though it doesn't detail the applicationName parameter beyond stating it's required.

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 tool's purpose: 'returns application by application name' with an optional namespace parameter. It specifies the verb ('returns') and resource ('application'), making the basic function understandable. However, it doesn't explicitly differentiate this tool from its many siblings like 'list_applications' or other get_application_* variants, which would require more specific scope clarification.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides some usage context by mentioning the optional namespace parameter for non-default namespaces, which implies when to use that parameter. However, it doesn't offer explicit guidance on when to choose this tool versus alternatives like 'list_applications' or other sibling tools that retrieve application-related information. The guidance is limited to parameter usage rather than tool selection.

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/argoproj-labs/argocd-mcp'

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