Skip to main content
Glama
argoproj-labs

argocd-mcp

Official

get_resource_events

Retrieve Kubernetes events for resources managed by ArgoCD applications to monitor deployment status and troubleshoot issues.

Instructions

get_resource_events returns events for a resource that is managed by an application

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
applicationNameYes
applicationNamespaceYesThe 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.
resourceUIDYes
resourceNamespaceYes
resourceNameYes

Implementation Reference

  • The core handler function that implements the logic to fetch events for a specific resource managed by an ArgoCD application via the ArgoCD API.
    public async getResourceEvents(
      applicationName: string,
      applicationNamespace: string,
      resourceUID: string,
      resourceNamespace: string,
      resourceName: string
    ) {
      const { body } = await this.client.get<V1EventList>(
        `/api/v1/applications/${applicationName}/events`,
        {
          appNamespace: applicationNamespace,
          resourceNamespace,
          resourceUID,
          resourceName
        }
      );
      return body;
    }
  • MCP tool registration for 'get_resource_events', including Zod input schema and wrapper handler that calls the ArgoCD client method.
    this.addJsonOutputTool(
      'get_resource_events',
      'get_resource_events returns events for a resource that is managed by an application',
      {
        applicationName: z.string(),
        applicationNamespace: ApplicationNamespaceSchema,
        resourceUID: z.string(),
        resourceNamespace: z.string(),
        resourceName: z.string()
      },
      async ({
        applicationName,
        applicationNamespace,
        resourceUID,
        resourceNamespace,
        resourceName
      }) =>
        await this.argocdClient.getResourceEvents(
          applicationName,
          applicationNamespace,
          resourceUID,
          resourceNamespace,
          resourceName
        )
    );
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. It only states that it 'returns events', without disclosing behavioral traits such as read-only vs. mutative nature, authentication needs, rate limits, error handling, or output format. This is inadequate for a tool with 5 parameters and no output schema, as it leaves critical operational details unspecified.

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, straightforward sentence that efficiently states the core function without unnecessary words. It's appropriately sized for a basic tool description, though it could be more front-loaded with key details given the complexity implied by 5 parameters.

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 the tool's complexity (5 parameters, no annotations, no output schema, low schema coverage), the description is incomplete. It doesn't explain what 'events' are, how they're returned, or any behavioral context, leaving significant gaps for an AI agent to understand and invoke the tool correctly in relation to its siblings.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is low at 20%, with only 'applicationNamespace' having a description. The tool description adds no parameter semantics beyond what's in the schema—it doesn't explain what 'resourceUID', 'resourceName', or other parameters mean in context, nor does it clarify relationships between parameters like 'applicationName' and 'resourceNamespace'. This fails to compensate for the schema's gaps.

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 events for a resource that is managed by an application', which provides a basic purpose (verb: returns, resource: events). However, it's vague about what 'events' entail (e.g., audit logs, status changes) and doesn't distinguish it from sibling tools like 'get_application_events' or 'get_application_managed_resources', leaving ambiguity in scope.

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?

No guidance is provided on when to use this tool versus alternatives. With siblings like 'get_application_events' and 'get_application_managed_resources', the description lacks context on differentiation (e.g., resource-level vs. application-level events). It also doesn't mention prerequisites or exclusions, leaving usage unclear.

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