Opsphere — DevOps & SRE Intelligence

ArgoCD: Debug connectivity

argocd_debug

Read-only

Tests connectivity to an ArgoCD instance by listing applications. Returns the resolved config (profile, context, namespace), reachability status, and app count. Useful for troubleshooting.

Input Schema

Name	Required	Description
`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.

Changed19 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 / appCount
```
Added value: +{
+  "minimum": 0,
+  "type": "integer"
+}
```

removedOutput schema / properties / data / properties / applications

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

addedOutput schema / properties / data / properties / apps

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "cluster": {
+        "type": "string"
+      },
+      "healthStatus": {
+        "enum": [
+          "Healthy",
+          "Progressing",
+          "Degraded",
+          "Suspended",
+          "Missing",
+          "Unknown"
+        ],
+        "type": "string"
+      },
+      "name": {
+        "type": "string"
+      },
+      "namespace": {
+        "type": "string"
+      },
+      "project": {
+        "type": "string"
+      },
+      "revision": {
+        "type": "string"
+      },
+      "syncStatus": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "name"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

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 / error
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / data / properties / gaps

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

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

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"
+}
```
addedOutput schema / properties / data / properties / reachable
```
Added value: +{
+  "type": "boolean"
+}
```

removedOutput schema / properties / data / properties / resources

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

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: +[
+  "reachable",
+  "appCount",
+  "apps",
+  "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.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description goes beyond that by disclosing what the call actually does internally (lists applications) and what it returns (resolved profile/context/namespace, reachability status, app count), which is genuinely useful. It omits any note on cost of listing many apps, but that is minor.

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?

Three short sentences, front-loaded with the core action and then the return payload. No filler, though the trailing "Useful for troubleshooting" is the weakest sentence.

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?

With an output schema present, detailed parameter descriptions, and read-only annotations, the description supplies what is needed to call the tool correctly. Only the sibling differentiation is missing, which is partially outside this tool's scope.

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% and each of the three optional parameters has a detailed description, so the schema carries the parameter burden. The tool description adds no parameter-level meaning, which matches the baseline 3.

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 names a specific verb and resource (tests connectivity to an ArgoCD instance via listing applications) and states the returned data. It is clear on its own, but it never references the sibling argocd_* tools (argocd_get_app, argocd_app_unhealthy, argocd_app_resources), so an agent must infer how it differs from them.

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?

"Useful for troubleshooting" implies the intended situation (diagnosing connectivity/config problems) but gives no explicit when-not or alternative routing among the many sibling argocd tools. Usage is only implied, not stated.

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?