Opsphere — DevOps & SRE Intelligence

ArgoCD: All App Resources

argocd_app_resources

Read-only

Returns ALL Kubernetes resources managed by an ArgoCD application — healthy and degraded alike. Unlike argocd_app_unhealthy (which filters to failing resources only), this tool shows the complete picture: every Deployment, Service, ConfigMap, Pod, etc. with its syncStatus and healthStatus. Includes a summary (counts by health state). Optional filters: kind and namespace.

Input Schema

Name	Required	Description
`kind`	No	Filter by Kubernetes resource kind (e.g. Deployment, Service, ConfigMap)
`name`	Yes	Application name (from argocd_list_apps or tenant catalog)
`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.
`namespace`	No	Filter by Kubernetes namespace
`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 / totalResources
```
Added value: +{
+  "minimum": 0,
+  "type": "integer"
+}
```
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",
+  "totalResources",
+  "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.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds that a summary of counts by health state is included and that each resource carries syncStatus and healthStatus, but it says nothing about behavior for large applications, result limits, or ordering.

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?

Front-loaded with the key scope statement and free of filler; the contrast with argocd_app_unhealthy and the filter mention each earn their place. Slightly longer than necessary given it partly restates return fields.

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?

A read-only tool with full schema coverage, annotations, and an output schema covering return shape — the description supplies the scope and the sibling distinction an agent needs to call it correctly. Only large-result behavior is left unaddressed, which is a minor gap.

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 coverage is 100%, so all six parameters are already documented in structured fields. The description only restates the kind and namespace filters and omits name, profile, instance, and context_id; with the schema doing the heavy lifting, this is the expected baseline.

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?

States a specific verb and resource (returns all Kubernetes resources managed by an ArgoCD application) and defines the scope precisely as healthy and degraded alike. It explicitly contrasts with the sibling argocd_app_unhealthy, so an agent can distinguish the two without opening a schema.

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

Usage Guidelines4/5

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

Names the alternative (argocd_app_unhealthy) and the condition that selects it — failing resources only versus the complete picture — and points to argocd_list_apps for the required name. It doesn't address when to prefer argocd_get_app or argocd_debug for app-level status, so routing is clear but not exhaustive.

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?