Skip to main content
Glama
vish288

mcp-argocd

by vish288
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Argocd Get Application Events

argocd_get_application_events
Read-onlyIdempotent

Retrieve Kubernetes events for an Argo CD application, newest first, to diagnose sync failures, errors, or health issues.

Instructions

Get Kubernetes events for an application, newest first, with messages capped at 500 chars.

Input Schema

NameRequiredDescriptionDefault
nameYesApplication name; accepts namespace/name for apps-in-any-namespace
limitNoMax results to return (1-200)
offsetNoResult offset for paging
projectNoProject; with it a missing app is 404 and a wrong-project app is 403
resource_uidNoResource UID
app_namespaceNoOverride appNamespace; defaults to ARGOCD_APP_NAMESPACE
resource_nameNoFilter to one resource
warnings_onlyNoOnly Warning events
resource_namespaceNoResource namespace

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.0
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "type": "object",
-  "x-fastmcp-wrap-result": true
-}New value: +null
  2. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld), so the bar is lower. The description still adds real behavioral context beyond them: results are ordered newest first and event messages are truncated at 500 characters, which affects what the agent can expect to read.

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?

A single front-loaded sentence with zero filler; the resource, ordering, and truncation constraint all appear immediately.

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

Completeness4/5

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

For a nine-parameter read tool with annotations covering safety and no output schema, the description is nearly sufficient. It omits mention of paging semantics (limit/offset interaction) and the warning-only filter, which is a minor gap given the schema documents them.

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 all nine parameters (limit, offset, project, warnings_only, resource filters, app_namespace) are already documented in the schema. The description adds no parameter syntax or interaction detail, so the baseline 3 applies.

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 states a specific verb+resource ('Get Kubernetes events for an application') plus two distinguishing behaviors: newest-first ordering and 500-char message cap. It does not explicitly contrast with siblings like argocd_get_pod_logs or argocd_get_resource, but no other sibling serves events, so ambiguity is low.

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?

Usage is only implied by the purpose statement; there is no explicit when-to-use, when-not-to-use, or routing to an alternative (e.g. pod logs vs application events). The agent can infer intent but gets no decision guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools