Skip to main content
Glama
argoproj-labs

argocd-mcp

Official

get_application_resource_tree

Retrieve the resource tree for an ArgoCD application by specifying its name to visualize and manage Kubernetes resources.

Instructions

get_application_resource_tree returns resource tree for application by application name

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
applicationNameYes

Implementation Reference

  • The core handler function that fetches the ArgoCD application resource tree via HTTP GET to the /resource-tree API endpoint.
    public async getApplicationResourceTree(applicationName: string) {
      const { body } = await this.client.get<V1alpha1ApplicationTree>(
        `/api/v1/applications/${applicationName}/resource-tree`
      );
      return body;
    }
  • MCP tool registration using addJsonOutputTool, including input schema validation with Zod and handler callback that delegates to ArgoCDClient.
      'get_application_resource_tree',
      'get_application_resource_tree returns resource tree for application by application name',
      { applicationName: z.string() },
      async ({ applicationName }) =>
        await this.argocdClient.getApplicationResourceTree(applicationName)
    );
  • Zod input schema for the tool: requires 'applicationName' as string.
    { applicationName: z.string() },
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It states the tool 'returns' data, implying a read-only operation, but does not disclose behavioral traits like error handling, rate limits, authentication needs, or what 'resource tree' entails. This leaves significant gaps for a tool with no structured safety hints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the core action. It avoids unnecessary words, though it could be more structured by explicitly separating purpose from usage. Every part earns its place, but brevity limits comprehensiveness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations, no output schema, and low schema coverage, the description is incomplete. It lacks details on return values, error cases, and behavioral context needed for effective use. For a tool in a set with many siblings, more guidance is warranted to ensure correct invocation.

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 description adds minimal meaning beyond the input schema, which has 0% coverage. It mentions 'by application name', clarifying that 'applicationName' is the key parameter, but does not explain format, constraints, or examples. With one parameter and low schema coverage, this provides basic context but insufficient detail.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool 'returns resource tree for application by application name', which specifies the verb ('returns'), resource ('resource tree'), and target ('application'). However, it does not differentiate from sibling tools like 'get_application' or 'get_application_managed_resources', leaving the scope vague. It avoids tautology by not merely restating the name.

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 does not mention prerequisites, exclusions, or compare to siblings such as 'get_application' or 'get_application_managed_resources'. Usage is implied only by the action described, with no explicit 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/argoproj-labs/argocd-mcp'

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