Opsphere — DevOps & SRE Intelligence

ArgoCD: Unhealthy resources in an Application

argocd_app_unhealthy

Read-only

Returns resources that are not Healthy or not Synced in an ArgoCD Application. Includes kind, namespace, name, status, health, message, and suggested next steps.

Input Schema

Name	Required	Description
`name`	Yes	Application name
`profile`	No	Optional AWS profile override for management-cluster kubectl authentication. OMIT to preserve the installation management identity (recommended). Do not substitute the destination account/environment profile. Explicit overrides are checked against configured valid_profiles. SSO requirements and Kubernetes permissions remain enforced.
`instance`	No	ArgoCD installation in the active workspace. Read opsphere://argocd/installations for mode and identifiers. In active mode, use an installation slug; an exact environment association or unique migrated alias is also accepted. Omit only when there is one installation. Legacy/shadow modes retain existing catalog aliases and defaults.
`context_id`	No	Optional explicit Connection Hub work context (ctx_*). Omit to use the conversation's active workspace; global Hub tools ignore it.

Output Schema

Name	Required	Description	Default
`ok`	Yes
`data`	Yes
`contractVersion`	Yes
`dataSchemaVersion`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed18 schema fields changedOct 26, 2026

changedOutput schema / properties / data / additionalProperties
```
Previous value: -trueNew value: +false
```

removedOutput schema / properties / data / properties / app

Removed value: -{
-  "$ref": "#/properties/data/properties/items/items"
-}

addedOutput schema / properties / data / properties / appName
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / data / properties / applications

Removed value: -{
-  "$ref": "#/properties/data/properties/items"
-}

removedOutput schema / properties / data / properties / clusters

Removed value: -{
-  "$ref": "#/properties/data/properties/items"
-}

removedOutput schema / properties / data / properties / count
```
Removed value: -{
-  "type": "number"
-}
```

addedOutput schema / properties / data / properties / gaps

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

removedOutput schema / properties / data / properties / items

Removed value: -{
-  "items": {
-    "additionalProperties": true,
-    "properties": {},
-    "type": "object"
-  },
-  "type": "array"
-}

addedOutput schema / properties / data / properties / partial
```
Added value: +{
+  "type": "boolean"
+}
```
removedOutput schema / properties / data / properties / resources / $ref
```
Removed value: -"#/properties/data/properties/items"
```

addedOutput schema / properties / data / properties / resources / items

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "health": {
+      "enum": [
+        "Healthy",
+        "Progressing",
+        "Degraded",
+        "Suspended",
+        "Missing",
+        "Unknown"
+      ],
+      "type": "string"
+    },
+    "kind": {
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "namespace": {
+      "type": "string"
+    },
+    "status": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "kind",
+    "name"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / data / properties / resources / type
```
Added value: +"array"
```

addedOutput schema / properties / data / properties / suggestions

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / data / properties / truncated
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / data / properties / warnings

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / data / required

Added value: +[
+  "appName",
+  "resources",
+  "suggestions",
+  "partial",
+  "truncated",
+  "warnings",
+  "gaps"
+]

addedOutput schema / properties / dataSchemaVersion

Added value: +{
+  "const": 2,
+  "type": "number"
+}

changedOutput schema / required

Previous value: -[
-  "contractVersion",
-  "ok",
-  "data"
-]New value: +[
+  "contractVersion",
+  "dataSchemaVersion",
+  "ok",
+  "data"
+]

First observedOct 15, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already establish that this is a safe read-only, non-destructive operation. The description adds that results include status, health, message, and suggested next steps, but it does not disclose edge behavior such as missing applications, empty results, or authentication/context requirements beyond what the schema already documents.

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 two sentences, front-loaded with the core filtering behavior, and every phrase contributes useful information. There is no repetition or filler.

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?

An output schema exists, so the description need not explain return values in depth, and annotations cover the safety profile. The schema also fully documents the application, profile, instance, and context parameters. The only minor gap is lack of explicit sibling routing guidance, but the definition is otherwise complete for a read-only diagnostic tool.

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 four parameters are already well documented in the input schema. The description adds no parameter-level meaning beyond what the schema provides, making the baseline 3 appropriate.

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

Purpose5/5

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

The description states a specific verb and resource: it returns resources that are not Healthy or not Synced in an ArgoCD Application. This clearly distinguishes it from the broader sibling argocd_app_resources by its unhealthy/un-synced filter without requiring schema inspection.

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 implies when this tool is useful by naming the unhealthy/un-synced condition, but it does not explicitly state when to choose it over argocd_app_resources, argocd_get_app, or argocd_debug. No exclusions or routing guidance are provided.

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

All Opsphere — DevOps & SRE Intelligence tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?